Triple
T31431535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | star out of Jacob |
E801809
|
entity |
| Predicate | originatesFromTribe |
P201931
|
FINISHED |
| Object | Jacob |
—
|
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: Jacob | Statement: [star out of Jacob, originatesFromTribe, Jacob]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromTribe Context triple: [star out of Jacob, originatesFromTribe, Jacob]
-
A.
hasTribeOrigin
chosen
Indicates that an entity originates from, or is ancestrally associated with, a particular tribe.
-
B.
tribeProgenitorOf
Indicates that one entity is the original ancestor or founding progenitor from which a particular tribe or tribal group descends.
-
C.
hasTribalAncestor
Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
-
D.
recognizedTribeIncludes
Indicates that a formally recognized tribe encompasses or includes a particular subgroup, member, or entity within its official structure or membership.
-
E.
tribalAffiliationType
Indicates the specific type or category of tribal affiliation that characterizes the relationship between an entity and a tribe.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00bf5990e08190a8b633e237656564 |
completed | May 10, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_6a00beef4f5881909b00ac89e6af5902 |
completed | May 10, 2026, 5:22 p.m. |
Created at: April 30, 2026, 8:58 p.m.