Triple
T2022953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graves classification |
E44144
|
entity |
| Predicate | originalNumberOfClassifiedEstates |
P24589
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [Graves classification, originalNumberOfClassifiedEstates, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNumberOfClassifiedEstates Context triple: [Graves classification, originalNumberOfClassifiedEstates, 16]
-
A.
originalNumberOfClasses
chosen
Indicates the initial total count of classes before any changes such as additions, removals, or merges occur.
-
B.
numberOfDeputiesFirstEstate
Indicates the quantity of deputies or representatives associated with the First Estate in a given context.
-
C.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
D.
numberOfHousingUnits
Indicates the total count of distinct housing units associated with an entity or within a specified area.
-
E.
numberOfHouses
Indicates the quantity of houses associated with a given entity or 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f1728481909ae36e821b9edef2 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.