Triple
T30570219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Beltran |
E778102
|
entity |
| Predicate | portrayedRank |
P110719
|
FINISHED |
| Object | Starfleet Commander |
—
|
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: Starfleet Commander | Statement: [Robert Beltran, portrayedRank, Starfleet Commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedRank Context triple: [Robert Beltran, portrayedRank, Starfleet Commander]
-
A.
representsRank
Indicates that one entity serves as the rank, status, or hierarchical level assigned to another entity.
-
B.
protagonistRank
Indicates the relative narrative importance or centrality of a character within a story, typically ranking how primary they are as a protagonist compared to others.
-
C.
roleInRanking
Indicates that an entity holds a specific position or function within a particular ranking or ordered list.
-
D.
rankingRole
chosen
Indicates that one entity holds a specific position or level in an ordered hierarchy or ranking relative to others.
-
E.
portrayedByCharacterType
Indicates that an entity is depicted or represented by a character of a specified type (e.g., hero, villain, sidekick) in a narrative or media work.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 29, 2026, 8:22 p.m.