Triple
T9799386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innovation Center Luxembourg |
E237796
|
entity |
| Predicate | productTypeResearched |
P31467
|
FINISHED |
| Object | tires |
—
|
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: tires | Statement: [Innovation Center Luxembourg, productTypeResearched, tires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productTypeResearched Context triple: [Innovation Center Luxembourg, productTypeResearched, tires]
-
A.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
-
B.
byProduct
Indicates that one entity is produced incidentally or as a secondary result of a process, activity, or creation involving another entity.
-
C.
typeOfSearch
Indicates the specific kind or category of search operation being performed or requested between entities.
-
D.
productTypeEvaluated
Indicates that an entity’s product type has been assessed or judged according to certain criteria or standards.
-
E.
productDomain
chosen
Indicates the domain, field, or area of application to which a given product belongs or is relevant.
- F. None of above.
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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda628fe0081909d2fbac3bd56ee84 |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.