Triple
T25758544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Numantia |
E648669
|
entity |
| Predicate | modernUseOfName |
P3657
|
FINISHED |
| Object | used for sports clubs in Soria |
—
|
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: used for sports clubs in Soria | Statement: [Numantia, modernUseOfName, used for sports clubs in Soria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernUseOfName Context triple: [Numantia, modernUseOfName, used for sports clubs in Soria]
-
A.
modernUse
chosen
Indicates how something is currently used or applied in modern times.
-
B.
modernNameForm
Indicates that one entity is the contemporary or currently used name form corresponding to another entity’s name.
-
C.
statusInModernUsage
Indicates how the usage or relevance of something is currently regarded or applied in contemporary contexts.
-
D.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
E.
modernNameOfficial
Indicates that an entity’s current, formally recognized name is the one specified.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 22, 2026, 4:43 a.m.