Triple
T25742979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gladstone’s Library |
E648267
|
entity |
| Predicate | hasResidentialRoomsCountApprox |
P51690
|
FINISHED |
| Object | over 20 |
—
|
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: over 20 | Statement: [Gladstone’s Library, hasResidentialRoomsCountApprox, over 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentialRoomsCountApprox Context triple: [Gladstone’s Library, hasResidentialRoomsCountApprox, over 20]
-
A.
approximateNumberOfRooms
chosen
Indicates an estimated or not precisely known count of rooms associated with an entity.
-
B.
hasNumberOfMainRooms
Indicates the relationship that specifies how many main rooms are present in a given entity, such as a building or dwelling.
-
C.
hasResidentialFloors
Indicates that an entity (such as a building or structure) includes one or more floors designated for residential use.
-
D.
numberOfBedrooms
Indicates the quantity of bedrooms associated with a given property or dwelling.
-
E.
numberOfResidentialFloors
Indicates the total count of floors in a building that are designated for residential use.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 22, 2026, 3:46 a.m.