Triple
T31431534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | star out of Jacob |
E801809
|
entity |
| Predicate | relatedToGroup |
P26016
|
FINISHED |
| Object | people of Israel |
E83090
|
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: people of Israel | Statement: [star out of Jacob, relatedToGroup, people of Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToGroup Context triple: [star out of Jacob, relatedToGroup, people of Israel]
-
A.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
relationshipWithOtherGroup
Indicates that one group has some defined connection, association, or interaction with another distinct group.
-
C.
refersToGroupAssociatedWith
Indicates that one entity makes reference to a group that is associated or linked with another specified entity.
-
D.
hasRelatedGroup
chosen
Indicates that one group or collection is associated with another group or collection through some defined relationship or connection.
-
E.
subgroupOrRelated
Indicates that one entity is a subgroup of, or otherwise closely related in group membership or classification to, 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b0778e5548190bb0576c7d2b0e93f |
completed | June 11, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 8:58 p.m.