Triple
T25617089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgan |
E642186
|
entity |
| Predicate | featureReductionComparedTo |
P28765
|
FINISHED |
| Object | Athlon |
—
|
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: Athlon | Statement: [Morgan, featureReductionComparedTo, Athlon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureReductionComparedTo Context triple: [Morgan, featureReductionComparedTo, Athlon]
-
A.
hasGreaterNoiseReductionThan
Indicates that one entity provides a higher level of noise reduction compared to another entity.
-
B.
featureLevelComparedTo
chosen
Indicates a comparative relationship between entities based on their feature level, specifying how one entity’s feature level ranks relative to another’s.
-
C.
visualReductionMethod
Indicates a method or technique used to reduce or simplify visual information or visual content.
-
D.
weightReductionComparedTo
Indicates a comparison showing how much less weight one entity has relative to another.
-
E.
comparisonAspect
Indicates that two or more entities are being compared specifically with respect to a particular shared attribute or dimension.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 21, 2026, 5 p.m.