Triple
T139550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lynx |
E2821
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | i.LINK |
E1455
|
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: i.LINK | Statement: [Lynx, alsoKnownAs, i.LINK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: i.LINK Context triple: [Lynx, alsoKnownAs, i.LINK]
-
A.
i.LINK
chosen
i.LINK is Sony’s brand name for the IEEE 1394 high-speed serial bus interface used for connecting digital audio, video, and data devices.
-
B.
i-lab
i-lab is Harvard University’s flagship innovation and entrepreneurship hub that provides students and affiliates with resources, mentorship, and space to develop and launch ventures.
-
C.
IJ Bay
IJ Bay is a body of water in the Netherlands that forms a key waterfront and harbor area for the city of Amsterdam.
-
D.
Nisshoki
Nisshoki, more commonly known as the Hinomaru, is the national flag of Japan featuring a red sun disc centered on a white field.
-
E.
IN
IN is the two-letter ISO 3166-1 alpha-2 country code representing India in international standards and systems.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257c679d88190bc71775dab2cfc64 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a2b4bc01cc8190bed2333b274ee645 |
completed | Feb. 28, 2026, 9:26 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.