Triple
T32342990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Michigan |
E826368
|
entity |
| Predicate | superstructure |
P73759
|
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: [USS Michigan, superstructure, single funnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: superstructure Context triple: [USS Michigan, superstructure, single funnel]
-
A.
superstructureType
chosen
Indicates the specific kind or design category of a structure’s superstructure that an entity possesses or is associated with.
-
B.
superstructureCondition
Indicates the physical state, integrity, or quality of the main structural framework of an object or construction.
-
C.
superstructureConstructedIn
Indicates that the construction of a superstructure took place at, within, or during a specified location, context, or time.
-
D.
topStructure
Indicates that one structure occupies the highest or most superior position relative to other structures within a given system or hierarchy.
-
E.
structuralAmbition
Indicates an entity’s intention or effort to change, shape, or influence an existing structure, system, or organizational framework.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 1, 2026, 12:48 a.m.