Triple
T35249767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | land of Tob |
E1018063
|
entity |
| Predicate | hasCharacterAssociated |
P198125
|
FINISHED |
| Object | Jephthah the Gileadite |
—
|
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: Jephthah the Gileadite | Statement: [land of Tob, hasCharacterAssociated, Jephthah the Gileadite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterAssociated Context triple: [land of Tob, hasCharacterAssociated, Jephthah the Gileadite]
-
A.
belongsToCharacter
Indicates that something is owned, associated with, or under the domain of a particular character.
-
B.
associatedWithCharacterGroup
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
C.
associatedWithCharacterAlias
Indicates that one entity is linked to or connected with an alternative name or alias used for a particular character.
-
D.
containsAssignedCharacters
Indicates that an entity includes or holds one or more characters that have been specifically assigned to it.
-
E.
associatedWithCharacterRole
Indicates that one entity has a connection or linkage to a specific character role played or held by another entity.
- F. None of above. chosen
Provenance (4 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
| PDg | Predicate description generation | batch_69fecb4be24481908bda6197d7fc32f4 |
completed | May 9, 2026, 5:51 a.m. |
Created at: May 3, 2026, 4:02 p.m.