Triple
T31882213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laish |
E813910
|
entity |
| Predicate | tribalAssociationAfterConquest |
P44753
|
FINISHED |
| Object | tribe of Dan |
—
|
NE NERFINISHED |
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 of Dan | Statement: [Laish, tribalAssociationAfterConquest, tribe of Dan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalAssociationAfterConquest Context triple: [Laish, tribalAssociationAfterConquest, tribe of Dan]
-
A.
tribeConfederation
Indicates a relationship where multiple tribes are united or organized together into a larger confederated group or alliance.
-
B.
hasTribalAssociation
chosen
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
C.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
D.
associatedTribalNation
Indicates a relationship where an entity is linked or connected to a specific tribal nation, typically reflecting affiliation, relevance, or jurisdiction.
-
E.
isTribalGovernmentOf
Indicates that a tribal government holds official governing authority over a specific tribe, community, or territory.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 30, 2026, 11:56 p.m.