Triple
T18120892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass-Observation |
E433726
|
entity |
| Predicate | periodOfMainActivity |
P95718
|
FINISHED |
| Object | late 1930s |
—
|
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: late 1930s | Statement: [Mass-Observation, periodOfMainActivity, late 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfMainActivity Context triple: [Mass-Observation, periodOfMainActivity, late 1930s]
-
A.
mainWorkPeriod
chosen
Indicates the primary or most significant span of time during which an entity is active, employed, or engaged in a particular work or role.
-
B.
periodReception
Indicates a temporal relationship where one entity receives, hosts, or is associated with another during a specific time period or interval.
-
C.
screenTimePhase
Indicates the specific stage or period within a broader screen-time process, session, or lifecycle that an entity is currently in.
-
D.
periodProperty
Indicates a temporal characteristic or attribute associated with a specific time period or interval.
-
E.
cycleOfActivity
Indicates a recurring sequence of actions or states that repeat over time as part of a process or behavior.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddea61bc8190af4b3efa2596b632 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.