Triple
T18377599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1896 Olympics men’s 100 metre freestyle |
E446356
|
entity |
| Predicate | startMethod |
P130902
|
FINISHED |
| Object | from boat |
—
|
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: from boat | Statement: [1896 Olympics men’s 100 metre freestyle, startMethod, from boat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startMethod Context triple: [1896 Olympics men’s 100 metre freestyle, startMethod, from boat]
-
A.
startProperty
Indicates that one entity marks the beginning or initial value/state of a property associated with another entity.
-
B.
startingGuard
Indicates that an entity serves as the primary or first-choice guard in a lineup, formation, or configuration.
-
C.
mainStartingPoint
Indicates the primary location or position from which an event, process, or path begins.
-
D.
implementationStart
Indicates the point in time or event at which the implementation of something (such as a plan, system, or project) begins.
-
E.
MPStart
Indicates the point in time or event at which a multi-part or multi-phase process, activity, or sequence begins.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5179919c881908d55ea24f93c5827 |
completed | April 19, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:45 a.m.