Triple
T15439692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XXX |
E369864
|
entity |
| Predicate | arabicNumeralEquivalent |
P38903
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [XXX, arabicNumeralEquivalent, 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arabicNumeralEquivalent Context triple: [XXX, arabicNumeralEquivalent, 30]
-
A.
RomanNumeral
Indicates that something is represented or written using the Roman numeral system.
-
B.
hasArabicNumeral
chosen
Indicates that an entity is associated with, represented by, or expressed using an Arabic numeral.
-
C.
numeralValueOfX
Indicates that a given numeral corresponds to, or represents, the numeric value of, the entity X.
-
D.
roleInRomanSystem
Indicates that one entity holds a specific function, position, or status within the structure or hierarchy of the Roman system.
-
E.
hasRomanEquivalent
Indicates that one entity corresponds to or is equivalent to another entity within the context of Roman culture, naming, or classification.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03eddf258819082679970b7d2b6af |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.