Triple
T18588022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Brave One |
E454286
|
entity |
| Predicate | hasPseudonymousCredit |
P70072
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Brave One, hasPseudonymousCredit, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPseudonymousCredit Context triple: [The Brave One, hasPseudonymousCredit, yes]
-
A.
hasCanonicalCredit
Indicates that a particular credit entry is the primary or officially recognized attribution for a work or contribution.
-
B.
hasCredit
Indicates that an entity possesses or is assigned a credit, such as financial credit, academic credit, or acknowledgment for a contribution.
-
C.
hasHiddenIdentity
Indicates that an entity possesses a secret or concealed identity that is not known to others.
-
D.
hasAlternativeCredit
Indicates that an entity is associated with a different or substitute form of credit or credit option than the primary one.
-
E.
pseudonymousAttribution
chosen
Indicates that an action, work, or statement is attributed to an entity using a pseudonym rather than their real identity.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b3e564819088e60fc25d1976f0 |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.