Triple
T26786615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Davenport |
E670396
|
entity |
| Predicate | strongestOf |
P57129
|
FINISHED |
| Object | Davenport bionic siblings |
—
|
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: Davenport bionic siblings | Statement: [Adam Davenport, strongestOf, Davenport bionic siblings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strongestOf Context triple: [Adam Davenport, strongestOf, Davenport bionic siblings]
-
A.
strongestOver
Indicates that one entity has greater strength or power than all other relevant entities in a given comparison set.
-
B.
strongestIn
Indicates that one entity possesses the greatest strength or power within a specified group, context, or comparison set.
-
C.
strongestMember
chosen
Indicates that one entity is the most powerful, capable, or dominant member within a specified group or set of entities.
-
D.
strongerThan
Indicates that one entity possesses greater strength, power, or intensity than another.
-
E.
strongerAt
Indicates that one entity has greater strength, power, or effectiveness than another in a specified context, condition, or domain.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61981c7e08190af1eeedcb257702a |
completed | May 2, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 4:13 a.m.