Triple
T33812000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toby the Tram Engine |
E866559
|
entity |
| Predicate | hasFaceLocation |
P194485
|
FINISHED |
| Object | front of tram body |
—
|
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: front of tram body | Statement: [Toby the Tram Engine, hasFaceLocation, front of tram body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFaceLocation Context triple: [Toby the Tram Engine, hasFaceLocation, front of tram body]
-
A.
hasFace
Indicates that one entity possesses, displays, or is characterized by a face.
-
B.
hasFacialProfile
Indicates that an entity possesses a specific facial profile or configuration of facial features.
-
C.
hasFaceDetectionAF
Indicates that an entity supports or uses autofocus functionality based on detecting human faces in the frame.
-
D.
faceCharacteristics
Indicates a relationship where specific attributes or features are associated with a face or facial appearance.
-
E.
faceVisibility
Indicates that one entity’s face is visible to another entity or from a particular viewpoint.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69fd76d0d7608190b350336d6c18182d |
completed | May 8, 2026, 5:38 a.m. |
Created at: May 1, 2026, 1:46 a.m.