Triple
T23391027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XXIV Squadron |
E594017
|
entity |
| Predicate | usesRomanNumeralDesignation |
P7356
|
FINISHED |
| Object | XXIV |
—
|
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: XXIV | Statement: [XXIV Squadron, usesRomanNumeralDesignation, XXIV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRomanNumeralDesignation Context triple: [XXIV Squadron, usesRomanNumeralDesignation, XXIV]
-
A.
usesRomanNumerals
chosen
Indicates that something represents numbers or sequences using the Roman numeral system rather than standard Arabic digits.
-
B.
hasRomanName
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
-
C.
usedInRomanPeriodFor
Indicates that something served a particular function, purpose, or application during the Roman period.
-
D.
hasRomanEquivalent
Indicates that one entity corresponds to or is equivalent to another entity within the context of Roman culture, naming, or classification.
-
E.
usesNumeralsFrom
Indicates that one writing system, notation, or representation employs the numeral symbols originating from another system.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49bdfec8190afa592c66660c279 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:36 p.m.