Triple
T32080418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XIII |
E819276
|
entity |
| Predicate | componentNumeralCount |
P42152
|
FINISHED |
| Object | three I characters |
—
|
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: three I characters | Statement: [XIII, componentNumeralCount, three I characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentNumeralCount Context triple: [XIII, componentNumeralCount, three I characters]
-
A.
numberDescribedAs
Indicates that a number is characterized, labeled, or referred to using a particular description or phrase.
-
B.
componentCountBasis
Indicates the rule or criterion used to determine how the number of components in something is counted or calculated.
-
C.
numberOfCounts
chosen
Indicates the total quantity or tally of discrete occurrences, items, or instances associated with an entity or event.
-
D.
usesNumeralsFrom
Indicates that one writing system, notation, or representation employs the numeral symbols originating from another system.
-
E.
articulationCount
Indicates the number of distinct articulations or jointed connections present between the related entities.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 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: May 1, 2026, 12:24 a.m.