Triple
T7969829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oga's Cantina |
E185294
|
entity |
| Predicate | timeLimitPolicy |
P22110
|
FINISHED |
| Object | limited visit duration per party |
—
|
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: limited visit duration per party | Statement: [Oga's Cantina, timeLimitPolicy, limited visit duration per party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeLimitPolicy Context triple: [Oga's Cantina, timeLimitPolicy, limited visit duration per party]
-
A.
timeLimited
chosen
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
B.
timeoutRule
Indicates a rule that defines when and under what conditions an operation, request, or process should automatically time out.
-
C.
storageLimitPolicy
Indicates the rules or constraints that govern how much and how long data or items may be stored.
-
D.
workHoursLimit
Indicates a constraint on the maximum number of hours an entity is allowed or scheduled to work within a specified period.
-
E.
refusalPeriodMaximum
Indicates the maximum allowed duration within which a refusal can occur or remain valid in the context of the related relationship or action.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd1c9a081909759e5bf5237204e |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:13 p.m.