Triple
T36958169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mancubus |
E914239
|
entity |
| Predicate | sizeRelativeToPlayer |
P186804
|
FINISHED |
| Object | much larger than player character |
—
|
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: much larger than player character | Statement: [Mancubus, sizeRelativeToPlayer, much larger than player character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sizeRelativeToPlayer Context triple: [Mancubus, sizeRelativeToPlayer, much larger than player character]
-
A.
playerBaseSize
Indicates the size or capacity of a player's base in a game or simulation context.
-
B.
sizeRelativeToPikmin
Indicates how the size of an entity compares to that of a Pikmin, typically expressing whether it is smaller, similar, or larger relative to a Pikmin.
-
C.
sizeRelativeToCourt
Indicates how the size of an entity compares to the size of a court.
-
D.
relativeSizeInFleet
Indicates the comparative size or capacity of an entity relative to other entities within the same fleet.
-
E.
relativeSizeOnTethys
Indicates how the size of one entity compares to another specifically in the context of Tethys.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.