Triple
T36485352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Lab |
E898919
|
entity |
| Predicate | supportsCrew |
P204896
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [US Lab, supportsCrew, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCrew Context triple: [US Lab, supportsCrew, true]
-
A.
hasExtendedCrew
Indicates that an entity is associated with an additional or supplementary group of crew members beyond its primary crew.
-
B.
providedCrewForMissionType
Indicates that an entity supplied or assigned crew members specifically for a particular type or category of mission.
-
C.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
-
D.
hasCrewBase
Indicates that an entity serves as the primary location or base of operations for a crew associated with another entity.
-
E.
carriesCrewOf
Indicates that one entity serves as the vehicle or vessel that transports the crew belonging to another entity.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.