Triple
T5530054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia and Reading Coal and Iron Company |
E145025
|
entity |
| Predicate | controlledAssetType |
P26628
|
FINISHED |
| Object | coal lands |
—
|
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: coal lands | Statement: [Philadelphia and Reading Coal and Iron Company, controlledAssetType, coal lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledAssetType Context triple: [Philadelphia and Reading Coal and Iron Company, controlledAssetType, coal lands]
-
A.
assetType
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
B.
ownsAssetType
chosen
Indicates that an entity possesses ownership rights over an asset of a specified type.
-
C.
coversAssetClass
Indicates that one entity (such as a product, service, or policy) includes, applies to, or provides coverage for a specified asset class.
-
D.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
E.
protectedAsset
Indicates that one entity serves as a safeguarded or defended resource in relation to another entity.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f996e088190844cba2c4458bd76 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.