Triple
T19699275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enneco |
E473046
|
entity |
| Predicate | onamasticField |
P116035
|
FINISHED |
| Object | Basque anthroponymy |
—
|
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: Basque anthroponymy | Statement: [Enneco, onamasticField, Basque anthroponymy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onamasticField Context triple: [Enneco, onamasticField, Basque anthroponymy]
-
A.
onamasticRole
chosen
Indicates a relationship where an entity holds a specific role or function within the system of naming or onomastics (e.g., as a name-bearer, name-giver, or type of name).
-
B.
overField
Indicates a spatial relationship where one entity is positioned above or extends across the area of a field.
-
C.
centeredOnField
Indicates that one entity is positioned or focused around the central area of a specified field or domain.
-
D.
locationOnField
Indicates the specific position or area that an entity occupies on a defined field or playing surface.
-
E.
rulingOnField
Indicates a decision or judgment made regarding a specific field, domain, or area of concern.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b426608190a46abec3652a6ca0 |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.