Triple
T27361558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ritz Hotel, Paris |
E685838
|
entity |
| Predicate | hasMottoOrReputation |
P176275
|
FINISHED |
| Object | symbol of luxury and elegance in Paris |
—
|
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: symbol of luxury and elegance in Paris | Statement: [Ritz Hotel, Paris, hasMottoOrReputation, symbol of luxury and elegance in Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoOrReputation Context triple: [Ritz Hotel, Paris, hasMottoOrReputation, symbol of luxury and elegance in Paris]
-
A.
hasMottoDepiction
Indicates that something visually represents or depicts the motto associated with an entity.
-
B.
mottoReputation
Indicates that a particular motto is associated with and characterizes the reputation or public image of an entity.
-
C.
hasMottoSymbol
Indicates that an entity’s motto is represented or accompanied by a particular symbol.
-
D.
hasMottoOrAssociation
chosen
Indicates a relationship where an entity is linked to a motto, slogan, or associated phrase that represents or characterizes it.
-
E.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 27, 2026, 11:54 a.m.