Triple
T6162778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merkið |
E137479
|
entity |
| Predicate | orientationOfCross |
P69144
|
FINISHED |
| Object | off-centre towards the hoist |
—
|
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: off-centre towards the hoist | Statement: [Merkið, orientationOfCross, off-centre towards the hoist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orientationOfCross Context triple: [Merkið, orientationOfCross, off-centre towards the hoist]
-
A.
orientationInducedBy
Indicates that the orientation of one entity is determined or caused by the orientation or configuration of another entity.
-
B.
orientedParallelTo
Indicates that one entity is parallel to another with a specified or consistent direction or orientation.
-
C.
crossingDirection
Indicates the direction in which one entity moves or passes across another reference point, boundary, or path.
-
D.
orientationPrinciple
Indicates the guiding rule or standard that directs how something is positioned, aligned, or oriented in relation to other things.
-
E.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d5e8edc8190a7a394ee832bac9f |
completed | March 22, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:17 p.m.