Triple
T28927504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemma Ward |
E733688
|
entity |
| Predicate | returnedToModeling |
P175998
|
FINISHED |
| Object | mid-2010s |
—
|
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: mid-2010s | Statement: [Gemma Ward, returnedToModeling, mid-2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToModeling Context triple: [Gemma Ward, returnedToModeling, mid-2010s]
-
A.
requiresModelingOf
Indicates that one entity depends on another entity being represented or simulated in a model in order for it to be properly defined, analyzed, or executed.
-
B.
tookHiatusFromModeling
Indicates that an individual temporarily paused or interrupted their modeling career or activities.
-
C.
returnedToUse
Indicates that something previously inactive, unavailable, or discontinued has been put back into active use or operation.
-
D.
returnedToRole
Indicates that an entity resumed or went back to a role or position it previously held.
-
E.
supportsModelingOf
Indicates that one entity provides the capability or functionality needed to represent, simulate, or model another entity or process.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 28, 2026, 8:25 a.m.