Triple
T24832778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaanxi Y-8 |
E621383
|
entity |
| Predicate | loadingConfiguration |
P25802
|
FINISHED |
| Object | rear loading ramp |
—
|
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: rear loading ramp | Statement: [Shaanxi Y-8, loadingConfiguration, rear loading ramp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadingConfiguration Context triple: [Shaanxi Y-8, loadingConfiguration, rear loading ramp]
-
A.
loader
Indicates a relationship where an entity is responsible for loading or placing items, data, or resources into another system, container, or context.
-
B.
loadingMechanism
chosen
Indicates the method or system by which something is loaded into or onto another object or structure.
-
C.
laterConfiguration
Indicates that one configuration occurs after another in time, representing a subsequent or later state relative to a prior configuration.
-
D.
loaderPosition
Indicates the spatial location or placement of a loader relative to a reference point or object.
-
E.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:16 a.m.