Triple
T4879539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Micah (Book of Judges) |
E109289
|
entity |
| Predicate | connectedEvent |
P10008
|
FINISHED |
| Object | migration of the Danites |
—
|
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: migration of the Danites | Statement: [Micah (Book of Judges), connectedEvent, migration of the Danites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedEvent Context triple: [Micah (Book of Judges), connectedEvent, migration of the Danites]
-
A.
connectedToEvent
chosen
Indicates that an entity has a direct association or linkage with a specific event.
-
B.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
C.
establishedOnEvent
Indicates that something (such as a relationship, status, or entity) was created, initiated, or formally established as a direct result of a specific event.
-
D.
connectsState
Indicates a relationship where one entity serves as a link or conduit between different states, conditions, or statuses of another entity.
-
E.
coordinateEvent
Indicates overseeing and organizing the planning, logistics, and execution of an event in collaboration with involved parties.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dbf37ac819085bb758bc6406271 |
completed | March 20, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.