Triple
T8721827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAMAS F1 |
E207028
|
entity |
| Predicate | ejectionPort |
P35739
|
FINISHED |
| Object | right side |
—
|
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: right side | Statement: [FAMAS F1, ejectionPort, right side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ejectionPort Context triple: [FAMAS F1, ejectionPort, right side]
-
A.
exhaustPosition
Indicates the spatial location or configuration of an exhaust outlet relative to the object it belongs to.
-
B.
portLocation
chosen
Indicates that a port is geographically situated at or associated with a specific location.
-
C.
canEject
Indicates that one entity has the ability or permission to forcibly remove or expel another entity from a place, system, or context.
-
D.
porte
Indicates that an entity carries, wears, or bears another entity (such as an object, attribute, or characteristic).
-
E.
exitsThrough
Indicates that an entity leaves or departs from a place, structure, or area by passing through a specified exit or passage.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d03f0848190a50c77e5cd028ee7 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.