Triple
T32459320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baline |
E829520
|
entity |
| Predicate | relatedNameOf |
P24023
|
FINISHED |
| Object | Irving Berlin’s birth surname |
—
|
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: Irving Berlin’s birth surname | Statement: [Baline, relatedNameOf, Irving Berlin’s birth surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedNameOf Context triple: [Baline, relatedNameOf, Irving Berlin’s birth surname]
-
A.
associatedName
chosen
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
B.
relatedNamedEntity
Indicates that two entities are connected through a shared or associated proper name (e.g., person, organization, location, or other named entity).
-
C.
relatedToNameType
Indicates that an entity has a relationship or association with a particular type or category of name.
-
D.
relationshipTarget
Indicates that an entity is the object or recipient toward which a specified relationship is directed.
-
E.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
- 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:57 a.m.