Triple
T8721790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GIAT Industries |
E207027
|
entity |
| Predicate | focusesOnCustomer |
P23437
|
FINISHED |
| Object | armed forces |
—
|
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: armed forces | Statement: [GIAT Industries, focusesOnCustomer, armed forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnCustomer Context triple: [GIAT Industries, focusesOnCustomer, armed forces]
-
A.
customerFocus
chosen
Indicates that one entity prioritizes understanding and meeting the needs, preferences, or satisfaction of another entity (typically a customer or client).
-
B.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
-
D.
customerValue
Indicates the degree of benefit, importance, or worth that a customer represents to a business or organization.
-
E.
exportCustomer
Indicates initiating the transfer or output of customer-related data from one system or context to another, typically for integration, backup, or reporting purposes.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d03f0848190a50c77e5cd028ee7 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.