Triple
T101319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American English |
E2045
|
entity |
| Predicate | hasNotableLexicalItem |
P4548
|
FINISHED |
| Object | elevator |
—
|
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: elevator | Statement: [American English, hasNotableLexicalItem, elevator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLexicalItem Context triple: [American English, hasNotableLexicalItem, elevator]
-
A.
hasNotableWord
chosen
Indicates that an entity is associated with a word or term that is considered notable, distinctive, or significant in some context.
-
B.
hasNotableSubject
Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
-
C.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
D.
hasSignificantLanguage
Indicates that an entity possesses a language that plays an important or primary role in its communication, identity, or functioning.
-
E.
hasConnotation
Indicates that one entity carries an implied or associated meaning, tone, or emotional nuance in relation to another 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2563921f8819087f720b1c803579f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.