Triple
T29995734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loop 202 |
E762015
|
entity |
| Predicate | isPartOfLoopSystem |
P195136
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Loop 202, isPartOfLoopSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfLoopSystem Context triple: [Loop 202, isPartOfLoopSystem, yes]
-
A.
isLoopOf
Indicates that one entity represents a loop or cyclic structure corresponding to, derived from, or associated with another entity.
-
B.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
C.
isOnLoopSide
Indicates that one entity is located on the side or segment of a loop structure relative to another reference point or element.
-
D.
partOfLoopWith
Indicates that one entity participates as a component or segment within the same loop structure as another entity.
-
E.
hasLoopRole
Indicates that an entity participates in a loop structure with a specific functional role within that loop.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
| PDg | Predicate description generation | batch_69fda945e1e08190bf923fcd4d2c548a |
completed | May 8, 2026, 9:13 a.m. |
Created at: April 29, 2026, 6:39 p.m.