Triple
T37459681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mimiron's Head |
E930885
|
entity |
| Predicate | requiresBoardSetup |
P202126
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mimiron's Head, requiresBoardSetup, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresBoardSetup Context triple: [Mimiron's Head, requiresBoardSetup, true]
-
A.
requiresManagementBoard
Indicates that something must be overseen, approved, or governed by a management board in order to proceed or be valid.
-
B.
requiresBoardCardsInHand
Indicates that a player must have specific board cards in their hand as a prerequisite for an action or state to be valid.
-
C.
hasBoardComposition
Indicates that an entity has a specific structure or makeup of its governing board, such as the types or proportions of members who serve on it.
-
D.
hasBoardType
Indicates that an entity is associated with or uses a specific type or category of board.
-
E.
onBoard
Indicates that one entity is physically located on or within a vehicle, vessel, or platform operated or used by another entity.
- 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_6a00532815c881908f10d9594458b3d7 |
completed | May 10, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a0052b9f030819081b8105bdcaf6d8f |
completed | May 10, 2026, 9:41 a.m. |
| PDg | Predicate description generation | batch_6a005326c1508190ace47b84c08b9565 |
completed | May 10, 2026, 9:43 a.m. |
Created at: May 3, 2026, 4:17 p.m.