Triple
T11050263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encino Man |
E261225
|
entity |
| Predicate | character |
P662
|
FINISHED |
| Object | Link |
E901346
|
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: Link | Statement: [Encino Man, character, Link]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Link Context triple: [Encino Man, character, 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 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.
-
C.
Link
Link is a core React Router component used to create navigational links in single-page React applications without triggering full page reloads.
-
D.
Link
Link is Sound Transit's light rail service that provides rapid transit connections across the Seattle metropolitan area.
-
E.
Link
chosen
Link is the thawed-out prehistoric caveman who becomes the central comedic figure adapting to modern life in the 1992 film "Encino Man."
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79868c78881908c8e3672c05ae7ec |
completed | April 9, 2026, 12:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3c851d5408190b12250a2a1322874 |
completed | April 18, 2026, 6:07 p.m. |
Created at: April 8, 2026, 9:26 p.m.