Triple
T1998672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bases Orgánicas de 1843 |
E43414
|
entity |
| Predicate | limitedRightsOf |
P9584
|
FINISHED |
| Object | citizens |
—
|
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: citizens | Statement: [Bases Orgánicas de 1843, limitedRightsOf, citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedRightsOf Context triple: [Bases Orgánicas de 1843, limitedRightsOf, citizens]
-
A.
hasLimitedAutonomyIn
Indicates that an entity operates or makes decisions within a domain where its freedom of action is constrained or controlled by another entity or governing context.
-
B.
limitedSystemType
Indicates that the system is restricted to a specific subset or category of system types, rather than allowing all possible types.
-
C.
accessRestriction
chosen
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
D.
restrictedFromUseFor
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
-
E.
accessRestrictedTo
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb79c97d48190b3147430ed39faa9 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.