Triple
T19693253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inception v1 |
E472887
|
entity |
| Predicate | achievedResultOn |
P1518
|
FINISHED |
| Object | ImageNet classification |
—
|
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: ImageNet classification | Statement: [Inception v1, achievedResultOn, ImageNet classification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedResultOn Context triple: [Inception v1, achievedResultOn, ImageNet classification]
-
A.
achievedOn
Indicates that a particular result, milestone, or state was successfully reached or completed at a specific time or date.
-
B.
achieved
chosen
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
-
C.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
E.
achievementStatus
Indicates the current state or level of completion of an achievement-related goal or milestone for an 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64211e5d481908358d922e0dca271 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.