Triple
T27872178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crait |
E704817
|
entity |
| Predicate | populationDuringSequelEra |
P23346
|
FINISHED |
| Object | effectively zero permanent inhabitants |
—
|
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: effectively zero permanent inhabitants | Statement: [Crait, populationDuringSequelEra, effectively zero permanent inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationDuringSequelEra Context triple: [Crait, populationDuringSequelEra, effectively zero permanent inhabitants]
-
A.
populationAfterDestruction
Indicates the size or composition of a population following an event of destruction or devastation.
-
B.
formerPopulation
chosen
Indicates that an entity once had a certain population value or size during a past time period but no longer does.
-
C.
lastKnownPopulations
Indicates the most recently recorded population counts associated with an entity or set of entities.
-
D.
populationBeforeDestruction
Indicates the number of individuals in a place or group prior to its destruction or elimination.
-
E.
populationAfterSiege
Indicates the number of people remaining in a place after a siege has concluded.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 27, 2026, 6:25 p.m.