Triple
T28309146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C8 IUR |
E713948
|
entity |
| Predicate | upperReceiverType |
P35429
|
FINISHED |
| Object | integrated upper receiver |
—
|
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: integrated upper receiver | Statement: [C8 IUR, upperReceiverType, integrated upper receiver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperReceiverType Context triple: [C8 IUR, upperReceiverType, integrated upper receiver]
-
A.
upperSectionType
Indicates the type or category assigned to the upper section or upper part of an object, structure, or entity.
-
B.
receiverType
chosen
Indicates the category or classification of the entity that receives something (such as a message, resource, or action) in the relationship.
-
C.
upperComponent
Indicates that one component is positioned above or on top of another component within a larger structure or assembly.
-
D.
upperBoundaryType
Indicates the kind or classification of the upper boundary that limits or caps a given range, interval, or extent.
-
E.
upperCourseOf
Indicates that one watercourse represents the upstream or higher-elevation segment of another watercourse within the same river system.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:39 p.m.