Triple
T29543549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMGTE Am (historic) |
E749567
|
entity |
| Predicate | minimumCrew |
P89118
|
FINISHED |
| Object | two drivers per car |
—
|
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: two drivers per car | Statement: [LMGTE Am (historic), minimumCrew, two drivers per car]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumCrew Context triple: [LMGTE Am (historic), minimumCrew, two drivers per car]
-
A.
intendedCrew
Indicates that an entity is designated or planned to serve as the crew for another entity (such as a vehicle, mission, or operation).
-
B.
crewRequired
chosen
Indicates that a certain number or type of crew members is necessary to operate or support the associated entity or activity.
-
C.
providedCrewForMissionType
Indicates that an entity supplied or assigned crew members specifically for a particular type or category of mission.
-
D.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
-
E.
hasExtendedCrew
Indicates that an entity is associated with an additional or supplementary group of crew members beyond its primary crew.
- F. None of above.
Provenance (3 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 5:05 p.m.