Triple
T29655195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nexus |
E750244
|
entity |
| Predicate | requiresWorkerType |
P11922
|
FINISHED |
| Object | Probe |
—
|
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: Probe | Statement: [Nexus, requiresWorkerType, Probe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresWorkerType Context triple: [Nexus, requiresWorkerType, Probe]
-
A.
hasWorkforceType
chosen
Indicates the type or category of workforce associated with an entity (such as permanent, temporary, contract, or part-time).
-
B.
supportsWorkloadType
Indicates that one entity is capable of handling, operating with, or being compatible with a specified type of workload.
-
C.
demandsToWorkWith
Indicates that one entity insists on or requires collaborating or being assigned to work with another specific entity.
-
D.
requiresFishType
Indicates that something must specify or depend on a particular type or category of fish in order to be valid or complete.
-
E.
multipleWorkingType
Indicates that an entity is associated with more than one type of work or employment classification simultaneously.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: April 28, 2026, 6:54 p.m.