Triple
T12738683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crawler-Transporter 2 |
E304430
|
entity |
| Predicate | corners |
P42380
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Crawler-Transporter 2, corners, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corners Context triple: [Crawler-Transporter 2, corners, 4]
-
A.
hasCorner
chosen
Indicates that one entity possesses or includes a corner that is part of or associated with another entity.
-
B.
locatedAtCornerOf
Indicates that one entity is positioned at or forms the corner where two or more boundaries, edges, or intersecting paths meet.
-
C.
hasSlowCorners
Indicates that an entity possesses corners or turning points that are navigated or traversed at a relatively low speed.
-
D.
cornerOfTriangle
Indicates that the subject is a vertex (corner point) belonging to a specific triangle.
-
E.
fourCornerCode
Indicates a standardized four-character code used to classify or identify something based on its four key components or positions.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.