Triple
T35280351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osha |
E1018917
|
entity |
| Predicate | takesTo |
P182681
|
FINISHED |
| Object | Rickon Stark to Last Hearth |
—
|
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: Rickon Stark to Last Hearth | Statement: [Osha, takesTo, Rickon Stark to Last Hearth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesTo Context triple: [Osha, takesTo, Rickon Stark to Last Hearth]
-
A.
takes
Indicates that one entity receives, accepts, or comes into possession of another entity.
-
B.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
C.
launchesTo
Indicates that one entity initiates the sending or propulsion of another entity toward a specific destination or into a particular trajectory.
-
D.
to
Indicates a directional or goal-oriented relationship in which something is directed, transferred, or oriented toward a target or endpoint.
-
E.
losesTo
Indicates that one entity is defeated by or comes out worse than another in a competitive or comparative context.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:03 p.m.