Triple
T8495278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Time of Changes |
E201082
|
entity |
| Predicate | hasMottoOrTaglineInText |
P23882
|
FINISHED |
| Object | “In our world there are no I’s.” |
—
|
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: “In our world there are no I’s.” | Statement: [A Time of Changes, hasMottoOrTaglineInText, “In our world there are no I’s.”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoOrTaglineInText Context triple: [A Time of Changes, hasMottoOrTaglineInText, “In our world there are no I’s.”]
-
A.
hasMottoInText
chosen
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
B.
hasTagline
Indicates that an entity is associated with a specific slogan or tagline that represents or promotes it.
-
C.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
D.
hasMottoContext
Indicates that an entity’s motto is associated with or applies within a specific contextual setting or scope.
-
E.
hasPartInMotto
Indicates that something is included as a component or element within a motto.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57dbe488190af5f06faf862cd5d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.