Triple
T29142783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The ka-tet of the Nineteen and Ninety-Nine |
E738680
|
entity |
| Predicate | hasMottoElement |
P191348
|
FINISHED |
| Object | Nineteen |
—
|
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: Nineteen | Statement: [The ka-tet of the Nineteen and Ninety-Nine, hasMottoElement, Nineteen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoElement Context triple: [The ka-tet of the Nineteen and Ninety-Nine, hasMottoElement, Nineteen]
-
A.
hasMottoContext
Indicates that an entity’s motto is associated with or applies within a specific contextual setting or scope.
-
B.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
C.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
D.
hasMottoSymbol
Indicates that an entity’s motto is represented or accompanied by a particular symbol.
-
E.
hasMottoScript
Indicates that an entity’s motto is written or expressed in a particular writing system or script.
- F. None of above. chosen
Provenance (4 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 28, 2026, 11:37 a.m.