Triple
T18099250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nostromo |
E433171
|
entity |
| Predicate | crewContract |
P405
|
FINISHED |
| Object | shares-based bonus system |
—
|
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: shares-based bonus system | Statement: [Nostromo, crewContract, shares-based bonus system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewContract Context triple: [Nostromo, crewContract, shares-based bonus system]
-
A.
launchContractor
Indicates that one entity serves as the contractor responsible for carrying out or managing the launch of another entity.
-
B.
typeOfContract
chosen
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
C.
contractUnit
Indicates that one entity serves as a contractual unit or party within a contract relationship involving another entity.
-
D.
typeOfContractor
Indicates the specific category or role of a contractor in relation to a given entity or project.
-
E.
contractValue
Indicates the monetary worth or agreed-upon financial amount specified in a contract between parties.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb521448190b97d2b2aa7e4d7e6 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.