Triple
T742250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribe of Judah |
E15267
|
entity |
| Predicate | roleInConquestNarrative |
P6060
|
FINISHED |
| Object | leading tribe in Book of Joshua |
—
|
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: leading tribe in Book of Joshua | Statement: [Tribe of Judah, roleInConquestNarrative, leading tribe in Book of Joshua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInConquestNarrative Context triple: [Tribe of Judah, roleInConquestNarrative, leading tribe in Book of Joshua]
-
A.
notableRiverCrossingRole
Indicates that an entity plays a significant role as a location or feature involved in the crossing of a river.
-
B.
worldWarIIRole
Indicates the specific role, position, or function an entity had in relation to World War II.
-
C.
roleInWarAndPeace
Indicates that an entity has a specific role or function within the context of the War and Peace conflict or narrative.
-
D.
conflictRole
chosen
Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
-
E.
roleInDialogue
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a60e286c81908787a41cf9b9f150 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fdaaf48190985f62acfc069508 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.