Triple
T17244348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guale people |
E418582
|
entity |
| Predicate | hadSocialOrganization |
P8216
|
FINISHED |
| Object | chiefdoms |
—
|
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: chiefdoms | Statement: [Guale people, hadSocialOrganization, chiefdoms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSocialOrganization Context triple: [Guale people, hadSocialOrganization, chiefdoms]
-
A.
hasSocialStructure
chosen
Indicates that an entity exhibits an organized pattern of social relationships or hierarchy among its members.
-
B.
societalOrganization
Indicates how a society is structured and organized in terms of its institutions, roles, and social relationships.
-
C.
hadOrganization
Indicates that an entity was affiliated with, employed by, or otherwise formally associated with a particular organization during some period of time.
-
D.
hasSocialPractice
Indicates that one entity engages in, follows, or is characterized by a particular social practice or customary pattern of social behavior.
-
E.
hasSocialGroup
Indicates that an entity belongs to, is associated with, or participates in a particular social group or community.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e22fb2c8190aea5d3872095bf46 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.