Triple
T24124397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacaso |
E597753
|
entity |
| Predicate | usePolicy |
P116336
|
FINISHED |
| Object | owners reserve stays through a digital scheduling system |
—
|
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: owners reserve stays through a digital scheduling system | Statement: [Pacaso, usePolicy, owners reserve stays through a digital scheduling system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usePolicy Context triple: [Pacaso, usePolicy, owners reserve stays through a digital scheduling system]
-
A.
usedPolicy
Indicates that an entity applied or followed a particular policy in carrying out an action or decision.
-
B.
publicPolicy
Indicates that an entity is a government or institutional rule, principle, or course of action intended to address public issues or guide societal outcomes.
-
C.
usesPolicyModel
Indicates that one entity applies, relies on, or operates according to a particular policy model.
-
D.
usagePolicy
chosen
Indicates the rules or conditions governing how something may be used or accessed.
-
E.
usesPolicyRate
Indicates that one entity applies or bases its actions or decisions on a specified policy interest rate.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee718f88190860d40c6f09a77c8 |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:06 p.m.