Triple
T26989247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss Universe national franchise |
E679820
|
entity |
| Predicate | mayLose |
P82574
|
FINISHED |
| Object | license for rule violations |
—
|
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: license for rule violations | Statement: [Miss Universe national franchise, mayLose, license for rule violations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayLose Context triple: [Miss Universe national franchise, mayLose, license for rule violations]
-
A.
canBeLostBy
chosen
Indicates that something is capable of being lost or forfeited by a particular entity.
-
B.
mayResultIn
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
-
C.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
-
D.
isLostBy
Indicates that something ceases to be possessed, controlled, or retained by a particular entity.
-
E.
maySucceed
Indicates that one entity has the potential or possibility to follow or replace another in a role, position, or sequence.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6218de4ec81908d3001e5b8748c7d |
completed | May 2, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69f611b07a808190af7c704bbdfe0587 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:50 a.m.