Triple
T28999827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moneen |
E736268
|
entity |
| Predicate | hasSplitReleaseWith |
P184598
|
FINISHED |
| Object | Alexisonfire |
—
|
NE NERFINISHED |
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: Alexisonfire | Statement: [Moneen, hasSplitReleaseWith, Alexisonfire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSplitReleaseWith Context triple: [Moneen, hasSplitReleaseWith, Alexisonfire]
-
A.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
B.
hasReleaseBranch
Indicates that an entity is associated with a specific release branch, typically representing a stabilized version line in a version control or release management system.
-
C.
hasSplit
Indicates that an entity has undergone a division into two or more distinct parts, groups, or components.
-
D.
hasSnippetReleasedOn
Indicates that a particular snippet was released or made publicly available on a specific date or time.
-
E.
hasScheduledReleases
Indicates that an entity has one or more releases planned to occur at specific future times.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 28, 2026, 9:34 a.m.