Triple
T2235596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leclerc main battle tank |
E49271
|
entity |
| Predicate | loaderType |
P25802
|
FINISHED |
| Object | autoloader |
—
|
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: autoloader | Statement: [Leclerc main battle tank, loaderType, autoloader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loaderType Context triple: [Leclerc main battle tank, loaderType, autoloader]
-
A.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
B.
loadingMechanism
chosen
Indicates the method or system by which something is loaded into or onto another object or structure.
-
C.
canBeLoadedAt
Indicates that an entity is capable of being placed onto or into another entity (such as a vehicle, container, or system) at a specific location or point in time.
-
D.
launchProvider
Indicates that one entity serves as the organization or company responsible for launching another entity (such as a spacecraft, satellite, or mission).
-
E.
mountType
Indicates the manner or configuration in which one object is mounted or attached to another.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc093ba0c819091df09a0e018fce1 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.