Triple
T15537185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Shell |
E370376
|
entity |
| Predicate | canFallOff |
P57509
|
FINISHED |
| Object | track edges |
—
|
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: track edges | Statement: [Green Shell, canFallOff, track edges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canFallOff Context triple: [Green Shell, canFallOff, track edges]
-
A.
fallsOn
Indicates that one entity descends due to gravity and comes to rest upon the surface of another entity.
-
B.
fallsOffAs
Indicates that one quantity decreases in value or intensity as another quantity increases or changes.
-
C.
fallsFrom
chosen
Indicates that one entity moves downward or drops starting from the location or position of another entity.
-
D.
eventuallyFalls
Indicates that an entity, after some passage of time or sequence of events, comes to fall or collapse.
-
E.
fallsIn
Indicates that one entity is located within, contained by, or geographically/administratively included inside another entity.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442f3c688190a599165e526af2ed |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.