Triple
T33552556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newton Haven |
E859377
|
entity |
| Predicate | hasInUniversePopulation |
P90440
|
FINISHED |
| Object | human residents |
—
|
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: human residents | Statement: [Newton Haven, hasInUniversePopulation, human residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInUniversePopulation Context triple: [Newton Haven, hasInUniversePopulation, human residents]
-
A.
hasInUniverseInhabitants
chosen
Indicates that a universe or fictional setting contains certain beings or populations as its inhabitants.
-
B.
hasGalaxyPopulation
Indicates that a galaxy possesses or is associated with a certain number or group of inhabitants or stellar objects constituting its population.
-
C.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
D.
inUniversePeople
Indicates that certain people exist or appear within a specified fictional or conceptual universe.
-
E.
hasPopulationOver
Indicates that one entity has a population greater than a specified number or than another entity.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
Created at: May 1, 2026, 1:40 a.m.