Triple
T9106315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arlanxeo |
E218485
|
entity |
| Predicate | keyApplication |
P86511
|
FINISHED |
| Object | tire manufacturing |
—
|
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: tire manufacturing | Statement: [Arlanxeo, keyApplication, tire manufacturing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyApplication Context triple: [Arlanxeo, keyApplication, tire manufacturing]
-
A.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
B.
keyUse
Indicates that one entity is used as a key or means of access, control, or identification for another entity.
-
C.
keyProgram
Indicates that a program or application is designated as a primary, central, or most important one within a given context or system.
-
D.
keyComponent
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
-
E.
keyProcess
Indicates that an entity plays a central, critical role in enabling or driving a particular process or workflow.
- F. None of above. chosen
Provenance (4 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca57286a88190b256d2461c5c0aed |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:16 p.m.