Triple
T5705340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carron Company |
E125769
|
entity |
| Predicate | hadPeakInfluence |
P55472
|
FINISHED |
| Object | late 18th century |
—
|
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: late 18th century | Statement: [Carron Company, hadPeakInfluence, late 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPeakInfluence Context triple: [Carron Company, hadPeakInfluence, late 18th century]
-
A.
hadPeakInfluencePeriod
chosen
Indicates the time span during which an entity exerted its greatest or most significant influence.
-
B.
hasSignificantInfluenceIn
Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
-
C.
hadInfluenceOn
Indicates that one entity affected, shaped, or contributed to the development, behavior, or characteristics of another entity.
-
D.
hasEnduringInfluenceOn
Indicates that one entity exerts a lasting, long-term impact on another entity’s state, development, or behavior.
-
E.
hasInfluentialStatus
Indicates that an entity holds a position, role, or condition that gives it significant influence or impact over others or over outcomes.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02459cd18819080fda0b481d11f08 |
completed | March 22, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.