Triple
T13538455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LOP-G |
E323320
|
entity |
| Predicate | crewTended |
P110754
|
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: [LOP-G, crewTended, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewTended Context triple: [LOP-G, crewTended, true]
-
A.
crewServed
Indicates that the operation or use of something requires a coordinated effort by multiple people acting together as a crew.
-
B.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
-
C.
crewOperated
Indicates that an entity is operated or controlled by a crew rather than autonomously or individually.
-
D.
crewMate
Indicates that two entities are members of the same crew or team, sharing a common group affiliation or working together in a joint capacity.
-
E.
crewChief
Indicates that one person serves as the lead or supervising crew chief responsible for directing and managing another person or group in an operational context.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafd7ad9481908fe1d7ffcf8fab71 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:45 p.m.