Triple
T32276761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pál Nagy |
E824569
|
entity |
| Predicate | componentGivenNameEquivalent |
P176360
|
FINISHED |
| Object | Pál is equivalent to Paul in English |
—
|
NE NERFINISHED |
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: Pál is equivalent to Paul in English | Statement: [Pál Nagy, componentGivenNameEquivalent, Pál is equivalent to Paul in English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentGivenNameEquivalent Context triple: [Pál Nagy, componentGivenNameEquivalent, Pál is equivalent to Paul in English]
-
A.
equivalentGivenName
chosen
Indicates that two given names are considered equivalent in meaning or usage, such as variants, transliterations, or alternative spellings of the same personal name.
-
B.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
C.
hasGivenNameEquivalence
Indicates that two entities share the same given (first) name or are considered equivalent with respect to their given names.
-
D.
equivalentSurname
Indicates that two entities share the same surname or are considered to have matching surnames for identification or equivalence purposes.
-
E.
equivalentIn
Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 1, 2026, 12:43 a.m.