Triple
T113669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Am Yisrael |
E2297
|
entity |
| Predicate | hasCollectiveResponsibilityConcept |
P531
|
FINISHED |
| Object | arevut (mutual responsibility) |
—
|
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: arevut (mutual responsibility) | Statement: [Am Yisrael, hasCollectiveResponsibilityConcept, arevut (mutual responsibility)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectiveResponsibilityConcept Context triple: [Am Yisrael, hasCollectiveResponsibilityConcept, arevut (mutual responsibility)]
-
A.
responsibleFor
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
B.
usedCollectiveName
Indicates that a group of entities is referred to by a shared collective name.
-
C.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
D.
isCollegialWith
Indicates a relationship where two entities interact in a cooperative, respectful, and professionally friendly manner, typically as peers or colleagues.
-
E.
hasOrganizationalStructure
Indicates that an entity possesses a defined internal arrangement of roles, responsibilities, and relationships that determine how it is organized and operates.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564417848190a8a8a38e97348963 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.