Triple
T31172687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourierist phalanx |
E794654
|
entity |
| Predicate | proposesPopulationSize |
P121182
|
FINISHED |
| Object | approximately 1,600 to 1,800 people |
—
|
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: approximately 1,600 to 1,800 people | Statement: [Fourierist phalanx, proposesPopulationSize, approximately 1,600 to 1,800 people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesPopulationSize Context triple: [Fourierist phalanx, proposesPopulationSize, approximately 1,600 to 1,800 people]
-
A.
envisionedPopulation
chosen
Indicates a relationship where an entity specifies or projects an expected or target population size for something (such as a place, project, or scenario).
-
B.
proposesPopulationLimit
Indicates that an entity suggests or advocates setting a maximum allowable size for a population.
-
C.
plannedPopulation
Indicates the intended or projected number of individuals expected to occupy or use something, such as a facility, area, or system, according to a plan.
-
D.
ensembleSize
Indicates the number of individual members or participants that make up a given group or ensemble.
-
E.
proposesNumberOfBoundaries
Indicates that an entity suggests or specifies a particular count of boundaries to be used or established in a given context.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 9:07 p.m.