Triple
T27139947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FRETILIN |
E681788
|
entity |
| Predicate | predecessorFullName |
P11166
|
FINISHED |
| Object | Associação Social-Democrata Timorense |
—
|
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: Associação Social-Democrata Timorense | Statement: [FRETILIN, predecessorFullName, Associação Social-Democrata Timorense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorFullName Context triple: [FRETILIN, predecessorFullName, Associação Social-Democrata Timorense]
-
A.
predecessorName
chosen
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
B.
predecessorRealName
Indicates that one entity is the real (actual) name of the predecessor of another entity.
-
C.
predecessorNameForm
Indicates that the value is a name or naming form previously used for the same entity before its current name.
-
D.
predecessorUser
Indicates that one user previously held a role, position, or state that is now held by another user, making the first user the predecessor of the second.
-
E.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 9:08 a.m.