Triple
T21704045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barefoot Marathoner of Rome |
E535727
|
entity |
| Predicate | bearerRanBarefootIn |
P144985
|
FINISHED |
| Object | 1960 Olympic marathon |
—
|
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: 1960 Olympic marathon | Statement: [Barefoot Marathoner of Rome, bearerRanBarefootIn, 1960 Olympic marathon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerRanBarefootIn Context triple: [Barefoot Marathoner of Rome, bearerRanBarefootIn, 1960 Olympic marathon]
-
A.
portrayedAsBarefoot
Indicates that an entity is depicted or represented without footwear, showing bare feet.
-
B.
isClimbedBarefootBySomePilgrims
Indicates that some pilgrims climb the referenced entity without wearing any footwear.
-
C.
runsBeneath
Indicates that one entity extends or moves below another entity along its length or span.
-
D.
bearerFounded
Indicates that the bearer (such as a person or organization) is the one who established or created the associated entity (such as a company, institution, or project).
-
E.
bearer
Indicates that one entity carries, holds, or possesses another entity, often as the current holder of a right, document, or object.
- F. None of above. chosen
Provenance (4 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b82901c81909de242c920fbc164 |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:46 p.m.