Triple
T28734906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midnight Club |
E730769
|
entity |
| Predicate | hasMottoInSeries |
P23882
|
FINISHED |
| Object | “To those before, to those after, to us now, and to those beyond.” |
—
|
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: “To those before, to those after, to us now, and to those beyond.” | Statement: [Midnight Club, hasMottoInSeries, “To those before, to those after, to us now, and to those beyond.”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoInSeries Context triple: [Midnight Club, hasMottoInSeries, “To those before, to those after, to us now, and to those beyond.”]
-
A.
hasMottoScript
Indicates that an entity’s motto is written or expressed in a particular writing system or script.
-
B.
mottoIncluded
Indicates that a motto is present as part of, or associated with, the referenced entity.
-
C.
hasMottoDepiction
Indicates that something visually represents or depicts the motto associated with an entity.
-
D.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
E.
hasMottoInText
chosen
Indicates that an entity has a motto expressed in a specific textual form or wording.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 28, 2026, 6 a.m.