Triple
T14948811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utoro |
E372735
|
entity |
| Predicate | hasAccommodationCapacity |
P73935
|
FINISHED |
| Object | significant relative to local population |
—
|
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: significant relative to local population | Statement: [Utoro, hasAccommodationCapacity, significant relative to local population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccommodationCapacity Context triple: [Utoro, hasAccommodationCapacity, significant relative to local population]
-
A.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
B.
hasResidenceCapacityFor
chosen
Indicates that an entity’s residence can accommodate or provide living space for a specified number or type of occupants.
-
C.
roomCapacity
Indicates the maximum number of people or occupants that a room is designed or allowed to hold.
-
D.
typicalHomeCapacity
Indicates the usual or standard number of occupants that a home is designed or expected to accommodate.
-
E.
hostOccupation
Indicates that one entity serves as the primary job, profession, or role held by 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68fae3c81909873b113bfcaca05 |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:39 a.m.