Triple
T22224365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Las Vegas |
E549294
|
entity |
| Predicate | bearerHasHonorificTitle |
P40137
|
FINISHED |
| Object | Mr. Las Vegas |
—
|
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: Mr. Las Vegas | Statement: [Mr. Las Vegas, bearerHasHonorificTitle, Mr. Las Vegas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerHasHonorificTitle Context triple: [Mr. Las Vegas, bearerHasHonorificTitle, Mr. Las Vegas]
-
A.
hasHonorificName
Indicates that an entity is referred to by a formal or respectful title or name used as an honorific.
-
B.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
C.
hasHonorificStatus
chosen
Indicates that an entity holds or is assigned a particular honorific title, rank, or status in relation to another entity.
-
D.
isHonorific
Indicates that one entity functions as an honorific title or respectful form of address applied to another entity.
-
E.
hasHonorificBasis
Indicates that one entity serves as the basis or justification for assigning an honorific title or respectful form of address 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b93e2208190aee70ffd82962ea0 |
completed | April 28, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.