Triple
T13330148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LYNX |
E317550
|
entity |
| Predicate | hasBrandName |
P40804
|
FINISHED |
| Object | LYNX |
E985200
|
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: LYNX | Statement: [LYNX, hasBrandName, LYNX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LYNX Context triple: [LYNX, hasBrandName, LYNX]
-
A.
LYNX
LYNX is a public bus transportation system serving the Orlando, Florida metropolitan area.
-
B.
Lynx Wildcat
The Lynx Wildcat is a modern British multi-role military helicopter used primarily by the Royal Navy and Army Air Corps for reconnaissance, attack, and maritime operations.
-
C.
Lynx
Lynx is a high-speed serial computer bus interface standard, better known as IEEE 1394 or FireWire, used for real-time data transfer between digital devices.
-
D.
Lynx
Lynx is a faint, northern constellation introduced by Johannes Hevelius, located between Ursa Major and Auriga in the night sky.
-
E.
Lynx
chosen
Lynx is a popular men’s grooming brand, known as Axe in many countries, offering deodorants, body sprays, and related personal care products.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9992e4f908190a6f172bf910cffb8 |
completed | April 11, 2026, 12:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f730641f588190886119506e6dde8f |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 9:30 p.m.