Triple
T35163439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | supreme council |
E1015329
|
entity |
| Predicate | mayBePermanent |
P187417
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [supreme council, mayBePermanent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBePermanent Context triple: [supreme council, mayBePermanent, true]
-
A.
maySucceed
Indicates that one entity has the potential or possibility to follow or replace another in a role, position, or sequence.
-
B.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
C.
mayBeRenewable
Indicates that an entity has the potential or option to be renewed, but is not guaranteed to be.
-
D.
possiblyBy
Indicates that an action, creation, or effect may have been caused or produced by a particular entity, but this attribution is uncertain or not definitively established.
-
E.
mayReverse
Indicates that an action, process, or state can be undone or returned to a previous condition.
- F. None of above. chosen
Provenance (4 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 3, 2026, 4:02 p.m.