Triple
T13777390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Brother Portugal |
E331043
|
entity |
| Predicate | eliminationProcess |
P126
|
FINISHED |
| Object | public vote |
—
|
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: public vote | Statement: [Big Brother Portugal, eliminationProcess, public vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliminationProcess Context triple: [Big Brother Portugal, eliminationProcess, public vote]
-
A.
loserElimination
Indicates that the entity identified as the loser in a competition, game, or contest is removed or disqualified from further participation.
-
B.
eliminationFormatUsed
Indicates that a particular elimination-style competition format (e.g., single or double elimination) is applied in organizing or conducting an event or contest.
-
C.
separationProcess
Indicates a process in which components of a mixture or system are divided or isolated from one another based on differing properties or conditions.
-
D.
reasonForElimination
Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
-
E.
selectionProcess
chosen
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0239cbfc81909064ac2457fdfff5 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.