Triple
T32256687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stargazer |
E824043
|
entity |
| Predicate | modificationBy |
P173889
|
FINISHED |
| Object | Orbital Sciences Corporation |
—
|
NE NERFINISHED |
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: Orbital Sciences Corporation | Statement: [Stargazer, modificationBy, Orbital Sciences Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modificationBy Context triple: [Stargazer, modificationBy, Orbital Sciences Corporation]
-
A.
modification
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
-
B.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
C.
showsModificationBy
Indicates that one entity displays or reveals the changes, alterations, or modifications that have been made by another entity.
-
D.
modifiedByCharacter
Indicates that something has been altered or influenced through the actions or behavior of a particular character.
-
E.
modificationRequires
Indicates that performing a modification on one entity is contingent upon satisfying a prerequisite condition or dependency involving 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc549ce88190963037034412e0b1 |
completed | May 3, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:41 a.m.