Triple
T36271591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-18 |
E892686
|
entity |
| Predicate | primaryFactoryLocation |
P47743
|
FINISHED |
| Object | Nazareth, Pennsylvania |
E892684
|
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: Nazareth, Pennsylvania | Statement: [D-18, primaryFactoryLocation, Nazareth, Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFactoryLocation Context triple: [D-18, primaryFactoryLocation, Nazareth, Pennsylvania]
-
A.
firstMajorProductionLocation
chosen
Indicates the location where an entity’s first major production or large-scale manufacturing activity took place.
-
B.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
C.
productionLocationType
Indicates the type or nature of the location where a product, item, or work is produced.
-
D.
primaryLocationIn
Indicates that an entity’s main or most significant location is within or at the referenced place.
-
E.
primaryPostingLocation
Indicates the main or default location where an entity (such as a message, job, or content item) is originally posted or primarily published.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a396e11be048190834adf68889be523 |
completed | June 22, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.