Triple
T7875777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC Davos |
E182846
|
entity |
| Predicate | hasHomeCapacityApprox |
P21034
|
FINISHED |
| Object | 7000 |
—
|
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: 7000 | Statement: [HC Davos, hasHomeCapacityApprox, 7000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeCapacityApprox Context triple: [HC Davos, hasHomeCapacityApprox, 7000]
-
A.
hasHomeCapacityVenue
Indicates that a venue has a specified capacity for accommodating people or events as its home location.
-
B.
hasResidenceCapacityFor
Indicates that an entity’s residence can accommodate or provide living space for a specified number or type of occupants.
-
C.
hasHomeFeature
Indicates that a home possesses or includes a particular feature or amenity.
-
D.
approximateCapacity
chosen
Indicates that one entity has an estimated or rough capacity value relative to another or to a specified measure.
-
E.
hasCapacityTo
Indicates that one entity possesses the ability, power, or potential to perform an action or bring about a particular effect in relation to another 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39aa7ca88190b88a18f6a8971e51 |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:57 p.m.