Triple
T37457661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quest Rogue |
E930838
|
entity |
| Predicate | boardPlan |
P189387
|
FINISHED |
| Object | develop wide boards of similar minions |
—
|
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: develop wide boards of similar minions | Statement: [Quest Rogue, boardPlan, develop wide boards of similar minions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardPlan Context triple: [Quest Rogue, boardPlan, develop wide boards of similar minions]
-
A.
floorPlan
Indicates that one entity serves as the architectural layout or room arrangement blueprint for another entity (such as a building or space).
-
B.
board
Indicates that an agent gets onto or into a vehicle, vessel, or craft in order to travel or be transported.
-
C.
wallPlan
Indicates a planned or designed configuration of walls within a space or structure.
-
D.
floorPlanType
Indicates the specific layout or configuration category that a floor plan belongs to (e.g., studio, 1-bedroom, open-plan).
-
E.
boardProperties
Indicates a relationship where specific attributes or characteristics are assigned to or associated with a board.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:17 p.m.