Triple
T14961038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noguchi table |
E373064
|
entity |
| Predicate | topForm |
P12789
|
FINISHED |
| Object | freeform triangular shape |
—
|
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: freeform triangular shape | Statement: [Noguchi table, topForm, freeform triangular shape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topForm Context triple: [Noguchi table, topForm, freeform triangular shape]
-
A.
formsTopOf
Indicates that one entity constitutes the uppermost part or surface of another entity.
-
B.
topForward
Indicates that one entity is positioned or oriented in front of and above another entity along a forward-facing direction.
-
C.
topLevel
Indicates that an entity occupies the highest or outermost level in a hierarchy, structure, or organizational arrangement, with no parent above it.
-
D.
topLocation
Indicates that one location is the primary, highest-level, or most prominent place associated with another entity or set of locations.
-
E.
typicalForm
chosen
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6cece6881908cd8c8fe41583bee |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:40 a.m.