Triple
T7673446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fretilin |
E173800
|
entity |
| Predicate | wonMajorityIn |
P17177
|
FINISHED |
| Object | 2001 Constituent Assembly election in East Timor |
—
|
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: 2001 Constituent Assembly election in East Timor | Statement: [Fretilin, wonMajorityIn, 2001 Constituent Assembly election in East Timor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonMajorityIn Context triple: [Fretilin, wonMajorityIn, 2001 Constituent Assembly election in East Timor]
-
A.
wonFor
Indicates that one entity received an award, prize, or recognition specifically on behalf of or representing another entity.
-
B.
hasMajority
Indicates that one entity holds more than half of the total share, control, or quantity in relation to another entity or set.
-
C.
wonBy
Indicates that a contest, game, or competition is decided in favor of a particular participant or side.
-
D.
hasMajorityIn
chosen
Indicates that one entity holds more than half of the control, ownership, or representation within another entity or group.
-
E.
hasMajorityOf
Indicates that one entity possesses or controls more than half of the total quantity, members, or share of another entity.
- 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.