Triple
T24420999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiryat Luza |
E615722
|
entity |
| Predicate | primaryResidentialCenterOf |
P128861
|
FINISHED |
| Object | Samaritans |
—
|
NE NERFINISHED |
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: Samaritans | Statement: [Kiryat Luza, primaryResidentialCenterOf, Samaritans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryResidentialCenterOf Context triple: [Kiryat Luza, primaryResidentialCenterOf, Samaritans]
-
A.
isMajorResidentialCenterOf
chosen
Indicates that a location serves as a primary hub or main area of residence for the referenced population or region.
-
B.
primaryTown
Indicates that a given town is the main or most important town associated with an entity (such as a person, organization, or region).
-
C.
centeredAtResidence
Indicates that an entity’s primary focus, activity, or presence is located at a specified residence.
-
D.
municipalCentre
Indicates that a location functions as the primary administrative or civic center for a municipality.
-
E.
isMajorCenterOf
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a34d3081908d6099365e2e4046 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:14 a.m.