Triple
T2657518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CECA |
E54648
|
entity |
| Predicate | supranationalCharacter |
P1413
|
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: [CECA, supranationalCharacter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supranationalCharacter Context triple: [CECA, supranationalCharacter, true]
-
A.
supranationalType
Indicates that one entity is classified as a specific type or category of supranational organization or authority in relation to another.
-
B.
hasSupranationalInstitution
chosen
Indicates that an entity is associated with or governed by an institution that operates above the level of individual nation-states.
-
C.
multiNationalState
Indicates a state whose population is composed of multiple distinct national or ethnic groups under a single political authority.
-
D.
recognizedAsSovereignWithin
Indicates that an entity is officially acknowledged as having sovereign authority or status within a specified domain, territory, or jurisdiction.
-
E.
underlyingIsMultinational
Indicates that the underlying entity operates in or is registered across multiple countries as a multinational organization.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd94c61a08190bdf5e1caeff3e788 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.