Triple
T29357916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ian Ward |
E744497
|
entity |
| Predicate | sharesNameBy |
P195492
|
FINISHED |
| Object | multiple individuals |
—
|
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: multiple individuals | Statement: [Ian Ward, sharesNameBy, multiple individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesNameBy Context triple: [Ian Ward, sharesNameBy, multiple individuals]
-
A.
sharesNameWith
Indicates that two entities have the same name or an identical naming designation.
-
B.
sharesNameTypeWith
Indicates that two entities have the same type or category of name (e.g., both are first names, both are surnames, or both are of the same naming convention).
-
C.
sharesNameRootWith
Indicates that two entities have names derived from the same linguistic root or base form.
-
D.
sharesGivenNameWith
Indicates that two entities have the same given (first) name.
-
E.
sharesNamePatternWith
Indicates that two entities have names that follow the same or a very similar structural or stylistic pattern.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69fdd5faea908190a17d77e050362ef5 |
completed | May 8, 2026, 12:24 p.m. |
Created at: April 28, 2026, 2:14 p.m.