Triple
T271724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B Loop |
E5647
|
entity |
| Predicate | complementsRoute |
P6117
|
FINISHED |
| Object | A 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: A Loop | Statement: [B Loop, complementsRoute, A Loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complementsRoute Context triple: [B Loop, complementsRoute, A Loop]
-
A.
complements
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
B.
auxiliaryRoutePattern
chosen
Indicates that one route serves as an auxiliary or supplemental path that follows or branches from a primary route according to a specific pattern or configuration.
-
C.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
D.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
E.
competesWith
Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25e69a9248190b9e7959b43223baa |
completed | Feb. 28, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69a25b721180819080d43c43fcbccf87 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.