Triple
T26195610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSO SO 4801 |
E655090
|
entity |
| Predicate | isOriginalIssueNumber |
P160032
|
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: [RSO SO 4801, isOriginalIssueNumber, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOriginalIssueNumber Context triple: [RSO SO 4801, isOriginalIssueNumber, true]
-
A.
issueNumber
Indicates the specific numeric identifier assigned to distinguish one issue from others within a series or collection.
-
B.
isOriginalMonoIssueOf
Indicates that one entity is the original monophonic (single-channel) issue or release from which another related version or issue is derived.
-
C.
firstIssueNumber
Indicates the issue number at which something (such as a series, feature, or character) first appeared or began.
-
D.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
E.
startsInIssue
Indicates that an event, process, or condition begins within the context or scope of a particular issue.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60ca5cd78819083f0216b359da470 |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:46 p.m.