Triple
T34892137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milton Security |
E1006313
|
entity |
| Predicate | employsFreelancers |
P185692
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Milton Security, employsFreelancers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employsFreelancers Context triple: [Milton Security, employsFreelancers, true]
-
A.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
B.
worksAsConsultantFor
Indicates that one entity provides professional consulting services to another entity, typically on a contractual or advisory basis.
-
C.
canHire
Indicates that one entity has the authority or ability to employ or recruit another entity.
-
D.
launchContractor
Indicates that one entity serves as the contractor responsible for carrying out or managing the launch of another entity.
-
E.
distributedWorksOf
Indicates that one entity disseminated, circulated, or handed out the works (such as creations, products, or materials) 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4 p.m.