Triple
T29273222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastasia |
E742174
|
entity |
| Predicate | superstateCount |
P244
|
FINISHED |
| Object | one of three superstates |
—
|
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: one of three superstates | Statement: [Eastasia, superstateCount, one of three superstates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: superstateCount Context triple: [Eastasia, superstateCount, one of three superstates]
-
A.
requiredNumberOfStates
Indicates the specific number of distinct states that something must have or support in order to meet a given requirement or condition.
-
B.
observerStateCount
Indicates the number of distinct states or conditions that an observer entity can occupy or register within the described context.
-
C.
stateSize
Indicates the relative or absolute physical extent or dimensions of a state, such as its area or population size.
-
D.
numberOfStates
chosen
Indicates the total count of distinct states or conditions associated with an entity or system.
-
E.
hasNumberOfStatesAndDistricts
Indicates a relationship where an entity is associated with a specific count of its constituent states and districts.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 12:49 p.m.