Triple
T19539254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pérez Pavón |
E488851
|
entity |
| Predicate | followsNamingTradition |
P78011
|
FINISHED |
| Object | Spanish naming customs |
—
|
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: Spanish naming customs | Statement: [Pérez Pavón, followsNamingTradition, Spanish naming customs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsNamingTradition Context triple: [Pérez Pavón, followsNamingTradition, Spanish naming customs]
-
A.
belongsToNamingTradition
chosen
Indicates that an entity is associated with or classified under a particular naming tradition or convention.
-
B.
followsFormalTradition
Indicates that one entity adheres to or complies with an established formal tradition, convention, or set of customary practices associated with another entity.
-
C.
followsRitualTraditionOf
Indicates that one entity practices, observes, or adheres to the ritual traditions established or maintained by another entity.
-
D.
followsCouncilTradition
Indicates that an entity adheres to established customs, practices, or precedents set by a council.
-
E.
traditionAscribes
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e638710b8c81908335535869fc9130 |
completed | April 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.