Triple
T13241874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Social Security |
E315297
|
entity |
| Predicate | coveredPopulation |
P769
|
FINISHED |
| Object | most U.S. workers |
—
|
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: most U.S. workers | Statement: [Social Security, coveredPopulation, most U.S. workers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredPopulation Context triple: [Social Security, coveredPopulation, most U.S. workers]
-
A.
hostsPopulation
Indicates that an entity serves as the living environment or container in which a particular population exists or resides.
-
B.
permanentPopulation
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
-
C.
livingPopulationDiscovered
Indicates that a living population of the entity was found or identified at a particular time or place.
-
D.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
E.
supportedPopulation
chosen
Indicates that one entity provides assistance, resources, or services to sustain or benefit a specified group of people.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d59e84c8190a9e547d0fe26a5f9 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.