Triple
T15140763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | fundamental charter |
E361675
|
entity |
| Predicate | canBeAdoptedThrough |
P59607
|
FINISHED |
| Object | constitutional assembly |
—
|
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: constitutional assembly | Statement: [fundamental charter, canBeAdoptedThrough, constitutional assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAdoptedThrough Context triple: [fundamental charter, canBeAdoptedThrough, constitutional assembly]
-
A.
canBeAdoptedBy
chosen
Indicates that one entity is eligible or allowed to be adopted by another entity.
-
B.
canAdopt
Indicates that one entity has the ability or permission to adopt another entity.
-
C.
adoptionType
Indicates the specific category or manner in which an adoption relationship is established or recognized between entities.
-
D.
adoptionStatus
Indicates the current state or outcome of an adoption relationship or process between entities.
-
E.
adopts
Indicates that one entity formally takes another into its care, control, or use, assuming ongoing responsibility or ownership.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005c46a248190a2364092d40274f3 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.