Triple
T31704472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurosam |
E809141
|
entity |
| Predicate | hasComponentSupplier |
P113314
|
FINISHED |
| Object | Thales Group |
E81227
|
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: Thales Group | Statement: [Eurosam, hasComponentSupplier, Thales Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentSupplier Context triple: [Eurosam, hasComponentSupplier, Thales Group]
-
A.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
-
B.
coreComponentSupplier
chosen
Indicates that one entity supplies essential or primary components to another entity.
-
C.
hasComponentModel
Indicates that an entity includes or is associated with a specific component model as part of its structure or configuration.
-
D.
hasFoundingComponent
Indicates that an entity includes another entity as a key element or constituent part involved in its founding or establishment.
-
E.
hasComponentCommunity
Indicates that an entity includes or is composed of a specific community as one of its constituent parts.
- F. None of above.
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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a030e31e01881909c6032532cd3c31a |
completed | May 12, 2026, 11:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e7fc54a68819085e49d75daa2799b |
completed | June 14, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a030dadea008190abe0a5652784bdd6 |
completed | May 12, 2026, 11:23 a.m. |
Created at: April 30, 2026, 11:13 p.m.