Triple
T37508142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Table |
E932148
|
entity |
| Predicate | missionSlotLimit |
P192108
|
FINISHED |
| Object | Limited number of concurrent adventures |
—
|
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 number of concurrent adventures | Statement: [Command Table, missionSlotLimit, Limited number of concurrent adventures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionSlotLimit Context triple: [Command Table, missionSlotLimit, Limited number of concurrent adventures]
-
A.
rideLimit
Indicates a constraint on the maximum number, duration, or frequency of rides permitted for an entity.
-
B.
visitorLimit
Indicates a constraint specifying the maximum number of visitors allowed for a given entity or context.
-
C.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
-
D.
launcherCapacity
Indicates the maximum number or size of items that a launcher is designed to hold or deploy.
-
E.
maximumSlotsRecommended
Indicates the highest number of slots that is advised or suggested to be used in a given context.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:17 p.m.