Triple
T26467523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Layth |
E665806
|
entity |
| Predicate | hasSociopoliticalForm |
P15721
|
FINISHED |
| Object | tribe |
—
|
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: tribe | Statement: [Layth, hasSociopoliticalForm, tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSociopoliticalForm Context triple: [Layth, hasSociopoliticalForm, tribe]
-
A.
hasPolity
Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
-
B.
socioPoliticalDomainOf
Indicates the socio-political sphere, context, or domain within which an entity, action, or relationship is situated or exerts influence.
-
C.
hasFormOfGovernmentContext
Indicates that an entity has a particular form of government specifically within a given contextual scope (such as a time period, jurisdiction, or situation).
-
D.
politicalForm
chosen
Indicates the type or structure of governance or political organization that characterizes an entity.
-
E.
associatedPoliticalSystem
Indicates that there exists a political system with which the subject is formally or conceptually connected.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 12:17 a.m.