Triple
T3385118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Dane |
E71280
|
entity |
| Predicate | spaceRequirements |
P47152
|
FINISHED |
| Object | needs large living space |
—
|
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: needs large living space | Statement: [Great Dane, spaceRequirements, needs large living space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceRequirements Context triple: [Great Dane, spaceRequirements, needs large living space]
-
A.
storageRequirement
Indicates the amount or type of storage capacity or resources that an entity needs in order to function or be maintained.
-
B.
occupancyRequirement
Indicates that a condition specifies how many or which entities must be present in or using a particular space or resource.
-
C.
bookingRequirement
Indicates that a particular condition, rule, or prerequisite must be satisfied in order to make or confirm a booking.
-
D.
capacityCategory
Indicates the classification of something based on the amount or volume it can hold, handle, or accommodate.
-
E.
spaceUsage
Indicates how much physical or storage space is occupied or utilized by an entity relative to the total available space.
- F. None of above. chosen
Provenance (4 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5ee5e188190912dcea494a12038 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada527ff308190813a7ffdcdec4322 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:14 p.m.