Triple
T31064061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasi Israel |
E791620
|
entity |
| Predicate | roleDesignation |
P974
|
FINISHED |
| Object | leader of Israel |
—
|
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: leader of Israel | Statement: [Nasi Israel, roleDesignation, leader of Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleDesignation Context triple: [Nasi Israel, roleDesignation, leader of Israel]
-
A.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
B.
roleDefines
Indicates that one role specifies, constrains, or determines the responsibilities, permissions, or behavior associated with another role or entity.
-
C.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
D.
hasDesignation
chosen
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
E.
roleAccordingTo
Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695792b748190882e715603d406a2 |
completed | May 3, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:01 p.m.