Triple
T27713635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nose |
E698757
|
entity |
| Predicate | appearanceFromDistance |
P311
|
FINISHED |
| Object | resembles the profile of a human nose |
—
|
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: resembles the profile of a human nose | Statement: [The Nose, appearanceFromDistance, resembles the profile of a human nose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearanceFromDistance Context triple: [The Nose, appearanceFromDistance, resembles the profile of a human nose]
-
A.
appearTo
Indicates that something gives the impression or seems to be a certain way to an observer, without confirming that it actually is so.
-
B.
appearanceInImages
Indicates that an entity is visually present or depicted within one or more images.
-
C.
isDistantObject
Indicates that one entity is located far away from another entity or reference point.
-
D.
depthApprox
Indicates an approximate or estimated depth relationship between entities, rather than an exact measured depth.
-
E.
appearance
chosen
Indicates how something looks or seems to an observer, including its visible form, condition, or outward impression.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 3:03 p.m.