Triple
T20679088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas area technology cluster |
E508240
|
entity |
| Predicate | laborPool |
P10129
|
FINISHED |
| Object | engineers |
—
|
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: engineers | Statement: [Dallas area technology cluster, laborPool, engineers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laborPool Context triple: [Dallas area technology cluster, laborPool, engineers]
-
A.
laborSet
Indicates that a particular labor, task, or work assignment has been designated or scheduled for an entity or context.
-
B.
laborProvision
chosen
Indicates the provision or supply of labor or workforce from one party to another for work or services.
-
C.
labourOf
Indicates that one entity is the work, effort, or labor performed or contributed by another entity.
-
D.
laborSystem
Indicates the type or structure of work organization, employment arrangements, and labor relations that govern how work is performed and managed.
-
E.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea516b88190b3e90d03fa981a44 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.