Triple
T3615951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermi Research Alliance, LLC |
E76599
|
entity |
| Predicate | typeOfContractor |
P50446
|
FINISHED |
| Object | national laboratory operator |
—
|
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: national laboratory operator | Statement: [Fermi Research Alliance, LLC, typeOfContractor, national laboratory operator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfContractor Context triple: [Fermi Research Alliance, LLC, typeOfContractor, national laboratory operator]
-
A.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
B.
primaryContractor
Indicates that one entity serves as the main responsible contractor for a project, agreement, or work in relation to another entity.
-
C.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
D.
employerType
Indicates the classification or category of an employer in relation to the entity (e.g., public, private, nonprofit, self-employed).
-
E.
launchContractor
Indicates that one entity serves as the contractor responsible for carrying out or managing the launch of 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27b5e008190a72a8dab7d736e64 |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:23 p.m.