Triple
T30646060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Read All About It (Part III) |
E780121
|
entity |
| Predicate | hasRomanNumeralInTitle |
P173678
|
FINISHED |
| Object | III |
—
|
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: III | Statement: [Read All About It (Part III), hasRomanNumeralInTitle, III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanNumeralInTitle Context triple: [Read All About It (Part III), hasRomanNumeralInTitle, III]
-
A.
titleInRomanNumerals
chosen
Indicates that an entity’s title is expressed or represented using Roman numerals.
-
B.
hasTitleInRevisedRomanization
Indicates that an entity has a specific title expressed using the Revised Romanization system for Korean.
-
C.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
D.
hasLatinTitle
Indicates that an entity possesses a title or name expressed in Latin.
-
E.
hasTitleLetter
Indicates that an entity possesses a specific letter or character within its title.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 29, 2026, 8:29 p.m.