Triple
T9799166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Goodyear |
E237790
|
entity |
| Predicate | improvedPropertyOf |
P6555
|
FINISHED |
| Object | elasticity of rubber |
—
|
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: elasticity of rubber | Statement: [Charles Goodyear, improvedPropertyOf, elasticity of rubber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: improvedPropertyOf Context triple: [Charles Goodyear, improvedPropertyOf, elasticity of rubber]
-
A.
improvesOn
chosen
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
B.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
-
C.
ownedPropertyWith
Indicates a relationship where one entity owns a particular property jointly or in association with another entity.
-
D.
enhancedBy
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
E.
builtProperty
Indicates that a constructed structure or building has been created on, or is associated with, a particular property or piece of land.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda627cc2c81909ccc2e26751f5e85 |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.