Triple
T5099055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilean Declaration of Independence |
E114936
|
entity |
| Predicate | hasLegalCharacter |
P17112
|
FINISHED |
| Object | unilateral act of secession |
—
|
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: unilateral act of secession | Statement: [Chilean Declaration of Independence, hasLegalCharacter, unilateral act of secession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalCharacter Context triple: [Chilean Declaration of Independence, hasLegalCharacter, unilateral act of secession]
-
A.
legalCharacter
chosen
Indicates that an entity possesses a status, role, or nature that is recognized and defined by law.
-
B.
hasLegalCodeCharacteristic
Indicates that a legal code possesses a specified characteristic, feature, or property.
-
C.
hasSpecialCharacter
Indicates that a given entity (such as a string or identifier) contains at least one non-alphanumeric special character.
-
D.
hasComponentCharacter
Indicates that one entity includes another entity as a constituent character or symbolic component.
-
E.
hasTypicalCharacterType
Indicates that an entity is commonly associated with or exemplified by a particular type of character or persona.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7568e9c881909f114973faef6832 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.