Triple
T4351688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opportunity District |
E98039
|
entity |
| Predicate | hasSubTheme |
P20138
|
FINISHED |
| Object | jobs of the future |
—
|
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: jobs of the future | Statement: [Opportunity District, hasSubTheme, jobs of the future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubTheme Context triple: [Opportunity District, hasSubTheme, jobs of the future]
-
A.
subtheme
chosen
Indicates that one topic or concept functions as a more specific, subordinate theme within a broader overarching theme.
-
B.
hasSubstyle
Indicates that one style is a more specific or subordinate variant of another style within a hierarchical style structure.
-
C.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
D.
hasThemeConnection
Indicates a relationship where one entity is linked to another through a shared or related theme, topic, or conceptual focus.
-
E.
hasSubSeries
Indicates that one series is a subordinate or component series within a larger parent series.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a99788819080b13a20124e49a0 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.