Triple
T31600140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plano Verão |
E806327
|
entity |
| Predicate | precededPlan |
P25144
|
FINISHED |
| Object | Plano Collor |
—
|
NE NERFINISHED |
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: Plano Collor | Statement: [Plano Verão, precededPlan, Plano Collor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededPlan Context triple: [Plano Verão, precededPlan, Plano Collor]
-
A.
wasPrecededBy
chosen
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
B.
precedentFor
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
-
C.
precededByPolicy
Indicates that one policy, event, or state occurs only after and in consequence of another specified policy having been established or taken effect.
-
D.
originalPlan
Indicates that one entity is the initial or primary plan or intended course of action associated with another entity.
-
E.
usedToPrecede
Indicates that one entity regularly or habitually came before another in time or sequence in the past.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 30, 2026, 10:32 p.m.