Triple
T35163440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | supreme council |
E1015329
|
entity |
| Predicate | mayBeAdHoc |
P171832
|
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, mayBeAdHoc, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeAdHoc Context triple: [supreme council, mayBeAdHoc, true]
-
A.
isAdHoc
chosen
Indicates that the relationship or action occurs in an improvised, informal, or non-standard manner, typically created for a specific purpose or situation rather than following a predefined structure.
-
B.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter another entity.
-
C.
mayBeAdaptedTo
Indicates that something has the potential or suitability to be modified or adjusted for use in a different context, condition, or purpose.
-
D.
mayBeExtended
Indicates that something has the potential or option to be lengthened in duration, scope, or size beyond its current or initial limits.
-
E.
mayAlsoBeCalled
Indicates that one entity can alternatively be referred to by another name or label.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:02 p.m.