Triple
T12418305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEOB |
E296694
|
entity |
| Predicate | isWorkplaceFor |
P93741
|
FINISHED |
| Object | federal civilian employees |
—
|
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: federal civilian employees | Statement: [NEOB, isWorkplaceFor, federal civilian employees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWorkplaceFor Context triple: [NEOB, isWorkplaceFor, federal civilian employees]
-
A.
locationOfWork
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
B.
officeIsIn
Indicates that one office is located within or inside another specified place or building.
-
C.
locationInWork
Indicates that one entity specifies the place or setting where another entity occurs, is situated, or takes place within a particular work (e.g., a scene’s location in a film or a chapter’s setting in a book).
-
D.
workAt
chosen
Indicates that an entity is employed by or performs work for a particular organization, company, or place.
-
E.
mayWorkIn
Indicates that an entity is allowed or has the possibility to work in a particular place, organization, or context.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.