Triple
T8548702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peta |
E202391
|
entity |
| Predicate | roleInIR8 |
P83248
|
FINISHED |
| Object | high-yielding parent of IR8 |
—
|
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: high-yielding parent of IR8 | Statement: [Peta, roleInIR8, high-yielding parent of IR8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInIR8 Context triple: [Peta, roleInIR8, high-yielding parent of IR8]
-
A.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
B.
ICAORole
Indicates a role or function that an entity holds within the context of ICAO (International Civil Aviation Organization) activities, structures, or regulations.
-
C.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
D.
roleInIntegration
Indicates the specific function or responsibility an entity has within a combined or coordinated system, process, or integration.
-
E.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
- F. None of above. chosen
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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe7529b648190b4b1cf1cb8836546 |
completed | March 31, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:19 p.m.