Triple
T36096592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOS-8 derived |
E1044077
|
entity |
| Predicate | systemsRole |
P12085
|
FINISHED |
| Object | platform for avionics and service systems integration |
—
|
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: platform for avionics and service systems integration | Statement: [DOS-8 derived, systemsRole, platform for avionics and service systems integration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemsRole Context triple: [DOS-8 derived, systemsRole, platform for avionics and service systems integration]
-
A.
systemRole
chosen
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
B.
systemStartRole
Indicates the role or function an entity assumes at the moment a system is started or initialized.
-
C.
siteRole
Indicates the specific function, responsibility, or position an entity holds within a particular site or location.
-
D.
serverRole
Indicates the functional role or responsibility that a server has within a system or network.
-
E.
platformRole
Indicates the specific function, position, or level of responsibility an entity holds within a given platform or 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.