Triple
T7403777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puffing Billy |
E170814
|
entity |
| Predicate | hasFrameType |
P76579
|
FINISHED |
| Object | wooden frame with iron components |
—
|
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: wooden frame with iron components | Statement: [Puffing Billy, hasFrameType, wooden frame with iron components]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrameType Context triple: [Puffing Billy, hasFrameType, wooden frame with iron components]
-
A.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
B.
hasHandleType
Indicates that one entity possesses or is characterized by a specific type or style of handle.
-
C.
hasFlowType
Indicates the type or category of flow associated with or exhibited by an entity.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasStandardType
Indicates that something conforms to or is categorized under a defined standard classification or type.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2701b108190be39174d4534f231 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f15c36d48190bc75353d3f67555a |
completed | March 27, 2026, 9:06 p.m. |
Created at: March 27, 2026, 3:10 p.m.