Triple
T25621732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burlington Industries, Inc. |
E642315
|
entity |
| Predicate | operatedMillsIn |
P180477
|
FINISHED |
| Object | North Carolina |
—
|
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: North Carolina | Statement: [Burlington Industries, Inc., operatedMillsIn, North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedMillsIn Context triple: [Burlington Industries, Inc., operatedMillsIn, North Carolina]
-
A.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
B.
minesOperatedBy
Indicates that a mine is operated or run by a particular organization or entity.
-
C.
operatedPipelinesIn
Indicates that an entity has operated or managed pipelines within a specified location or jurisdiction.
-
D.
operatedStationsIn
Indicates that an entity managed or ran the operations of one or more stations within a specified area or system.
-
E.
operatedMintIn
Indicates that an entity operated or managed a minting facility or operation within a specified location or jurisdiction.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 21, 2026, 5:05 p.m.