Triple
T33068774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passalaqua |
E846174
|
entity |
| Predicate | isBirthNameSurnameOf |
P18679
|
FINISHED |
| Object | Joe Pass |
—
|
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: Joe Pass | Statement: [Passalaqua, isBirthNameSurnameOf, Joe Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBirthNameSurnameOf Context triple: [Passalaqua, isBirthNameSurnameOf, Joe Pass]
-
A.
isSurname
Indicates that one entity is the family name (last name) of another entity.
-
B.
isMatronymicOf
Indicates that one entity is a name or designation derived from the mother of another entity, typically used as that entity’s family or identifying name.
-
C.
bearerBirthNameOf
Indicates that one entity is the birth name originally given to and borne by another entity.
-
D.
appliesToPersonBirthName
chosen
Indicates that the referenced value is used as the birth name of the specified person.
-
E.
equivalentSurname
Indicates that two entities share the same surname or are considered to have matching surnames for identification or equivalence purposes.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.