Triple
T38325392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wawona (1897) |
E1036768
|
entity |
| Predicate | hasHullConstruction |
P6097
|
FINISHED |
| Object | wooden hull |
—
|
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 hull | Statement: [Wawona (1897), hasHullConstruction, wooden hull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHullConstruction Context triple: [Wawona (1897), hasHullConstruction, wooden hull]
-
A.
hasEngineeringHull
Indicates that an entity possesses an engineering hull as a distinct structural or functional component.
-
B.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
-
C.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
D.
hasHullType
chosen
Indicates that an entity possesses or is characterized by a specific type or form of hull.
-
E.
hasTopConstruction
Indicates that one entity serves as the uppermost structural element or construction positioned on top of 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.