Triple
T18142858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvin |
E434304
|
entity |
| Predicate | isAssociatedWithFieldThroughNamesake |
P113714
|
FINISHED |
| Object | artificial intelligence |
—
|
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: artificial intelligence | Statement: [Marvin, isAssociatedWithFieldThroughNamesake, artificial intelligence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithFieldThroughNamesake Context triple: [Marvin, isAssociatedWithFieldThroughNamesake, artificial intelligence]
-
A.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
B.
surnameAssociatedWithField
chosen
Indicates that a particular surname is commonly linked or connected to a specific professional, academic, or activity-related field.
-
C.
inSameFieldAs
Indicates that two entities work, study, or specialize within the same professional or academic field.
-
D.
namedForField
Indicates that one entity is named after, or in honor of, a particular field, discipline, or area of study.
-
E.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de0da3e081908732ed022f5eb90a |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.