Triple
T33263661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rifleman's Creed |
E851588
|
entity |
| Predicate | authorService |
P58602
|
FINISHED |
| Object | United States Marine Corps |
—
|
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: United States Marine Corps | Statement: [Rifleman's Creed, authorService, United States Marine Corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorService Context triple: [Rifleman's Creed, authorService, United States Marine Corps]
-
A.
authorType
Indicates the specific role or category of authorship associated with an entity, such as primary author, co-author, or editor.
-
B.
authorStatus
Indicates the role or standing an individual holds as an author, such as their level of contribution, recognition, or current authorship state in relation to a work.
-
C.
publishesAuthor
Indicates that a publisher or publishing entity issues, releases, or makes publicly available works created by a specific author.
-
D.
authorBelongsTo
chosen
Indicates that an author is affiliated with, or is a member of, a particular organization, group, or entity.
-
E.
authorName
Indicates the name associated with the person or entity that authored a given work or resource.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 1, 2026, 1:32 a.m.