Triple
T18584180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyrule Warriors |
E454195
|
entity |
| Predicate | hasCharacter |
P2308
|
FINISHED |
| Object | Young Link |
E114496
|
NE 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: Young Link | Statement: [Hyrule Warriors, hasCharacter, Young Link]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Young Link Context triple: [Hyrule Warriors, hasCharacter, Young Link]
-
A.
Link
Link is a TAG Heuer watch collection known for its distinctive S-shaped bracelet design and blend of sporty elegance.
-
B.
Link
Link is Sound Transit's light rail service that provides rapid transit connections across the Seattle metropolitan area.
-
C.
Link
chosen
Link is the heroic, green-clad protagonist of Nintendo’s The Legend of Zelda series, known for wielding the Master Sword and saving the kingdom of Hyrule.
-
D.
Link
Link is a surname shared by various notable individuals across fields such as architecture, science, and the arts.
-
E.
Link
Link is a core React Router component used to create navigational links in single-page React applications without triggering full page reloads.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543d200dc8190b8797d731f4e4865 |
completed | April 19, 2026, 9:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a05037ae9708190afa199491cb93343 |
completed | May 13, 2026, 11:04 p.m. |
Created at: April 10, 2026, 11:44 a.m.