Triple
T36368860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellevue Sanatorium |
E895698
|
entity |
| Predicate | hasMottoOrEthos |
P33142
|
FINISHED |
| Object | emphasis on patient individuality |
—
|
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: emphasis on patient individuality | Statement: [Bellevue Sanatorium, hasMottoOrEthos, emphasis on patient individuality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoOrEthos Context triple: [Bellevue Sanatorium, hasMottoOrEthos, emphasis on patient individuality]
-
A.
hasMottoLikeFunction
chosen
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
B.
hasMottoElement
Indicates that something includes a specific phrase or component as part of its motto.
-
C.
mottoIncluded
Indicates that a motto is present as part of, or associated with, the referenced entity.
-
D.
hasMottoTradition
Indicates that an entity possesses a traditional motto associated with its identity or heritage.
-
E.
hasMottoSymbol
Indicates that an entity’s motto is represented or accompanied by a particular symbol.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:10 p.m.