Triple
T37964582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naniwa-class cruiser |
E947102
|
entity |
| Predicate | hasSuperstructureFeature |
P6684
|
FINISHED |
| Object | single funnel |
—
|
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: single funnel | Statement: [Naniwa-class cruiser, hasSuperstructureFeature, single funnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperstructureFeature Context triple: [Naniwa-class cruiser, hasSuperstructureFeature, single funnel]
-
A.
hasSuperstructurePosition
Indicates the relative location or placement of a component or element within the superstructure of an object or system.
-
B.
hasArchitecturalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
C.
hasSuperstructureColor
Indicates that one entity has a superstructure whose color is the value specified by the other entity.
-
D.
superstructureType
Indicates the specific kind or design category of a structure’s superstructure that an entity possesses or is associated with.
-
E.
superstructureCondition
Indicates the physical state, integrity, or quality of the main structural framework of an object or construction.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a007241df8081909dbad651fda82aa7 |
completed | May 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_6a0071e77ed081908cd618da8977d878 |
completed | May 10, 2026, 11:54 a.m. |
Created at: May 3, 2026, 4:20 p.m.