Triple
T109536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fife Circle Line |
E2214
|
entity |
| Predicate | loopShape |
P1464
|
FINISHED |
| Object | circular route with two coastal arms |
—
|
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: circular route with two coastal arms | Statement: [Fife Circle Line, loopShape, circular route with two coastal arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loopShape Context triple: [Fife Circle Line, loopShape, circular route with two coastal arms]
-
A.
controlStructure
Indicates a relationship where one entity governs, regulates, or directs the behavior, operation, or flow of another entity or process.
-
B.
shape
chosen
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
-
C.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
D.
leafShape
Indicates the characteristic form or outline of a leaf that an entity possesses or exhibits.
-
E.
inForceUntil
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563fd2fc819090265edbfe3092d6 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.