Triple
T5689360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brasília Time |
E125390
|
entity |
| Predicate | isBehind |
P65959
|
FINISHED |
| Object | UTC |
—
|
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: UTC | Statement: [Brasília Time, isBehind, UTC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBehind Context triple: [Brasília Time, isBehind, UTC]
-
A.
locatedBehind
Indicates that one entity is positioned at the rear of or on the far side of another entity along a given viewing or reference direction.
-
B.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
C.
operatedBehind
Indicates that one entity performed an operation or action while being physically or figuratively positioned at the rear or out of direct view of another entity.
-
D.
installedInFrontOf
Indicates that one object has been placed or mounted so that it is positioned directly in front of another object.
-
E.
backedFor
Indicates that one entity provides support, endorsement, or backing for another entity, often in a financial, political, or strategic context.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:44 p.m.