Triple
T21542129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 10 Loop |
E531517
|
entity |
| Predicate | hasLoopDesignation |
P122164
|
FINISHED |
| Object | Loop |
—
|
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: Loop | Statement: [SR 10 Loop, hasLoopDesignation, Loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoopDesignation Context triple: [SR 10 Loop, hasLoopDesignation, Loop]
-
A.
hasLoopRole
Indicates that an entity participates in a loop structure with a specific functional role within that loop.
-
B.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
C.
hasLoopConfiguration
chosen
Indicates that an entity is associated with a specific loop setup or arrangement that defines how a loop operates or is structured.
-
D.
hasInclinedLoop
Indicates that one entity features or contains a loop that is positioned at an angle rather than being level or vertical.
-
E.
hasVerticalLoops
Indicates that one entity features or includes vertical loop structures in its form, design, or configuration.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb58c34808190b0eb54ba01e2cc13 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:28 p.m.