Triple
T30413399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ber |
E773681
|
entity |
| Predicate | pairedWithName |
P169189
|
FINISHED |
| Object | Dov-Ber |
—
|
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: Dov-Ber | Statement: [Ber, pairedWithName, Dov-Ber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairedWithName Context triple: [Ber, pairedWithName, Dov-Ber]
-
A.
pairedNickname
Indicates that two entities share or are associated with a complementary or matching set of nicknames.
-
B.
pairedSingleWith
Indicates that one entity is matched or associated as a single counterpart with another single entity, typically forming an exclusive one-to-one pairing.
-
C.
pairedWithFunctionally
Indicates that one entity is functionally matched or coupled with another to perform a complementary or corresponding role.
-
D.
pairedField
Indicates that one field is logically linked or associated with another field as a corresponding pair.
-
E.
pairedReleaseWith
Indicates that two items are released together as a coordinated or associated pair.
- F. None of above. chosen
Provenance (4 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686478d64819084a68bcd9c02bd8a |
completed | May 2, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:05 p.m.