Triple
T34376481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishmael |
E882298
|
entity |
| Predicate | associatedWithPeoples |
P77482
|
FINISHED |
| Object | Ishmaelites |
E51332
|
NE 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: Ishmaelites | Statement: [Ishmael, associatedWithPeoples, Ishmaelites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPeoples Context triple: [Ishmael, associatedWithPeoples, Ishmaelites]
-
A.
associationWithHumans
Indicates a general relationship, connection, or involvement between an entity and one or more humans.
-
B.
peopleAssociatedWith
chosen
Indicates that there exists some form of connection, involvement, or relationship between the referenced people.
-
C.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
D.
associatedBeings
Indicates that two or more beings are linked or connected to each other in some relevant way.
-
E.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
- F. None of above.
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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a371822ebe08190bded971671ab6da0 |
completed | June 20, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:59 a.m.