Triple
T4359805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lod |
E98635
|
entity |
| Predicate | hasEthnicTensionHistory |
P55763
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lod, hasEthnicTensionHistory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicTensionHistory Context triple: [Lod, hasEthnicTensionHistory, yes]
-
A.
religiousConflictBetween
Indicates a relationship where two entities are in opposition or dispute due to differing religious beliefs, practices, or affiliations.
-
B.
conflictHistory
Indicates a history of conflict or antagonistic interactions that have occurred between the related entities.
-
C.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
D.
historicallyContestedBy
Indicates that two or more parties have disputed or challenged control, ownership, or interpretation of something over a period of history.
-
E.
religiousConflictPeriod
Indicates a period of time during which conflicts or hostilities occur that are primarily motivated or structured by religious differences or tensions.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e1bfa48190bb506d9ca1ed7b6a |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:16 p.m.