Triple
T5382467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carron Company |
E113118
|
entity |
| Predicate | hasSiteUse |
P62923
|
FINISHED |
| Object | later industrial and commercial uses |
—
|
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: later industrial and commercial uses | Statement: [Carron Company, hasSiteUse, later industrial and commercial uses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiteUse Context triple: [Carron Company, hasSiteUse, later industrial and commercial uses]
-
A.
currentSiteUse
Indicates how a site is presently being used or the function it currently serves.
-
B.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
C.
hasObservationSite
Indicates that something (such as a measurement, event, or observation activity) is associated with or took place at a specific observation site or location.
-
D.
hasAdministrationSite
Indicates the specific location or site on or in a subject where a substance, treatment, or intervention is administered.
-
E.
hasModernSiteUse
Indicates that an entity is currently used or functions in a particular way at a modern site or location.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86d163f88190939638d44fcb24a7 |
completed | March 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd853005088190b1b092a9beb090b2 |
completed | March 20, 2026, 5:34 p.m. |
Created at: March 20, 2026, 2:03 p.m.