Triple
T35643142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLS core stage |
E1029928
|
entity |
| Predicate | manufacturingSiteLocation |
P181529
|
FINISHED |
| Object | New Orleans, Louisiana |
—
|
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: New Orleans, Louisiana | Statement: [SLS core stage, manufacturingSiteLocation, New Orleans, Louisiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manufacturingSiteLocation Context triple: [SLS core stage, manufacturingSiteLocation, New Orleans, Louisiana]
-
A.
manufacturingSite
chosen
Indicates the location or facility where a product is or was manufactured.
-
B.
mainManufacturingSite
Indicates the primary location where an entity’s products are manufactured or produced.
-
C.
firstMajorProductionLocation
Indicates the location where an entity’s first major production or large-scale manufacturing activity took place.
-
D.
hasPrimaryProductionLocation
Indicates that an entity’s main or principal place where it is produced or manufactured is a specified location.
-
E.
engineeringLocation
Indicates the place where engineering-related work, design, or technical development for an entity is carried out.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f4d48548190a2b332aefc390b01 |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.