Triple
T21359585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fragment: The Island |
E526733
|
entity |
| Predicate | playerActivity |
P100358
|
FINISHED |
| Object | exploring an island |
—
|
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: exploring an island | Statement: [The Fragment: The Island, playerActivity, exploring an island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerActivity Context triple: [The Fragment: The Island, playerActivity, exploring an island]
-
A.
playerActivities
chosen
Indicates the various actions, events, or engagements that a player participates in within a given context or system.
-
B.
playerStatus
Indicates the current state or condition of a player within a game or system, such as their activity, health, or participation status.
-
C.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
D.
hasInGameActivities
Indicates that an entity includes or offers specific activities or actions that can be performed within a game context.
-
E.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
- 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee5bac9e1481909121e89f046c77f6 |
completed | April 26, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:07 p.m.