Triple
T18768288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 48-1385 |
E458946
|
entity |
| Predicate | hasNoseShape |
P20675
|
FINISHED |
| Object | bullet-shaped nose similar to original X-1 |
—
|
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: bullet-shaped nose similar to original X-1 | Statement: [48-1385, hasNoseShape, bullet-shaped nose similar to original X-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoseShape Context triple: [48-1385, hasNoseShape, bullet-shaped nose similar to original X-1]
-
A.
noseType
chosen
Indicates the specific shape or classification of a nose that an entity possesses.
-
B.
hasNoseExtension
Indicates that one entity possesses or is characterized by an extension or protruding part of the nose.
-
C.
noseLength
Indicates the length or size of an entity’s nose, typically as a measurable physical attribute.
-
D.
hasColorOfNose
Indicates that one entity possesses a nose whose color matches or is characterized by the specified color entity.
-
E.
nostrilOrientation
Indicates the directional alignment or facing angle of an entity’s nostrils relative to a reference frame or axis.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d867264819098ae35c9feab3bb4 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.