Triple
T28701640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Schilder |
E729565
|
entity |
| Predicate | hasDuoName |
P46169
|
FINISHED |
| Object | Nick & Simon |
—
|
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: Nick & Simon | Statement: [Nick Schilder, hasDuoName, Nick & Simon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDuoName Context triple: [Nick Schilder, hasDuoName, Nick & Simon]
-
A.
hasOfficialDualNameWith
Indicates that two entities share an officially recognized dual or joint name used in formal contexts.
-
B.
hasGivenNameCombination
Indicates that an entity is associated with a specific combination or sequence of given (first) names.
-
C.
bilingualName
Indicates that an entity has a name expressed in two different languages, linking the entity to its bilingual designation.
-
D.
formedDuoWith
Indicates that two entities joined together to create a duo, typically collaborating or acting as a pair for a shared purpose or activity.
-
E.
associatedWithDuo
chosen
Indicates a relationship in which an entity is linked or connected to a specific duo, typically implying involvement, collaboration, or relevance to that pair.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f656b5405881908b22cbcf723bff61 |
completed | May 2, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:42 a.m.