Triple
T26335368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howard Eiland |
E662504
|
entity |
| Predicate | coTranslatorWith |
P128309
|
FINISHED |
| Object | Kevin McLaughlin |
—
|
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: Kevin McLaughlin | Statement: [Howard Eiland, coTranslatorWith, Kevin McLaughlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coTranslatorWith Context triple: [Howard Eiland, coTranslatorWith, Kevin McLaughlin]
-
A.
coTranslatedWith
chosen
Indicates that two or more entities were translated together as part of the same translation effort, project, or work.
-
B.
translator
Indicates that one entity serves to convert or render content from one language or form into another for a second entity.
-
C.
textTranslation
Indicates a relationship where one text is rendered into another language or form while preserving its original meaning.
-
D.
translationActivity
Indicates that an entity is engaged in the process of translating content from one language or form into another.
-
E.
canTranslateBetween
Indicates that an entity has the ability to translate or convert information accurately between two specified languages, formats, or representation systems.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f6cf3208190816114685e00e96c |
completed | May 2, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:36 p.m.