Triple
T36977824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Current Employment Statistics survey |
E914745
|
entity |
| Predicate | collectionMode |
P152671
|
FINISHED |
| Object | online reporting |
—
|
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: online reporting | Statement: [Current Employment Statistics survey, collectionMode, online reporting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionMode Context triple: [Current Employment Statistics survey, collectionMode, online reporting]
-
A.
collectionFormed
Indicates that multiple items or entities have been gathered and organized together into a defined collection.
-
B.
collectionBy
Indicates that one entity is the collector or curator responsible for assembling, managing, or owning a particular collection of items represented by another entity.
-
C.
collectionKind
Indicates the type or category of collection to which an entity or group of entities belongs.
-
D.
collectionMethods
chosen
Indicates the ways or procedures by which something is gathered, obtained, or collected.
-
E.
collectionScope
Indicates the extent, boundaries, or range over which a collection (such as a set of items, data, or resources) is defined or intended to apply.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:14 p.m.