Triple
T322203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFC |
E6436
|
entity |
| Predicate | aliasInContext |
P2919
|
FINISHED |
| Object | GPIB IFC line |
—
|
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: GPIB IFC line | Statement: [IFC, aliasInContext, GPIB IFC line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aliasInContext Context triple: [IFC, aliasInContext, GPIB IFC line]
-
A.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
B.
alsoWrittenAs
Indicates that one entity has an alternative written form, spelling, or notation represented by the other entity.
-
C.
actsOnBehalfOf
Indicates that one entity performs actions or makes decisions as a representative or proxy for another entity.
-
D.
alternativeTransliteration
Indicates that one written form represents an alternative way of transliterating the same original text or name into another script or orthography.
-
E.
contextOf
chosen
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.