Triple
T19582837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stranger in a Strange Land |
E490037
|
entity |
| Predicate | hasMottoOrKeyPhrase |
P132650
|
FINISHED |
| Object | Thou art God |
—
|
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: Thou art God | Statement: [Stranger in a Strange Land, hasMottoOrKeyPhrase, Thou art God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoOrKeyPhrase Context triple: [Stranger in a Strange Land, hasMottoOrKeyPhrase, Thou art God]
-
A.
hasSloganOrKeyPhrase
chosen
Indicates that an entity is associated with a specific slogan, tagline, or key phrase used to represent or promote it.
-
B.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
C.
hasMottoSymbol
Indicates that an entity’s motto is represented or accompanied by a particular symbol.
-
D.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
E.
hasMottoAuthority
Indicates that an entity has the official power or right to establish, approve, or oversee the use of a motto for 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6404e18f88190b7fec59499dd25e8 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.