Triple
T24806958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson solids |
E620679
|
entity |
| Predicate | haveMixedFaceTypes |
P76192
|
FINISHED |
| Object | often |
—
|
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: often | Statement: [Johnson solids, haveMixedFaceTypes, often]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveMixedFaceTypes Context triple: [Johnson solids, haveMixedFaceTypes, often]
-
A.
hasTwoMainFaces
Indicates that an entity possesses exactly two primary or most prominent faces or sides.
-
B.
hasCodeMixingType
Indicates the specific type or pattern of code mixing present in a multilingual utterance or text.
-
C.
hasNumberOfTypes
chosen
Indicates that an entity is associated with a specific count of distinct types or categories it possesses or includes.
-
D.
hasHybridUses
Indicates that an entity is used in both traditional (e.g., physical or analog) and modern or alternative (e.g., digital, renewable, or mixed-mode) ways or contexts.
-
E.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:50 a.m.