Triple
T18381136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunis Eyalet |
E446446
|
entity |
| Predicate | deFactoAutonomy |
P5082
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Tunis Eyalet, deFactoAutonomy, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deFactoAutonomy Context triple: [Tunis Eyalet, deFactoAutonomy, high]
-
A.
grantsOfAutonomy
Indicates that one entity confers a degree of self-governance, independence, or decision-making authority to another entity.
-
B.
autonomyStatus
chosen
Indicates the degree to which an entity operates independently or with self-governed control, without external direction or intervention.
-
C.
autonomyDemand
Indicates a request or assertion by one party to have independent control or self-governance in a situation or relationship.
-
D.
governedByDeFacto
Indicates that an entity is effectively controlled or ruled in practice by another entity, regardless of formal or legal authority.
-
E.
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.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5179b60f88190adf39e85375bd11b |
completed | April 19, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:45 a.m.