Triple
T15838546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köroghlu |
E384042
|
entity |
| Predicate | transportInLegend |
P11822
|
FINISHED |
| Object | heroic horse |
—
|
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: heroic horse | Statement: [Köroghlu, transportInLegend, heroic horse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportInLegend Context triple: [Köroghlu, transportInLegend, heroic horse]
-
A.
transportsCharacter
Indicates that one entity moves or carries a character from one location or state to another.
-
B.
withinTravelTo
Indicates that one location is close enough to another that traveling between them is feasible or practical within a specified limit (such as time or distance).
-
C.
transportFrom
Indicates that something or someone is moved or carried away starting from a specified origin location.
-
D.
transportHubType
Indicates the specific category or kind of transport hub associated with an entity (e.g., airport, train station, bus terminal).
-
E.
transportFor
chosen
Indicates a relationship where one entity serves as the means or service used to move another entity from one place to another.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e4fa24819086a1a226082ac2d3 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.