Triple
T23212123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbara Gordon |
E580623
|
entity |
| Predicate | roleAsOracle |
P124074
|
FINISHED |
| Object | information hub for superheroes |
—
|
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: information hub for superheroes | Statement: [Barbara Gordon, roleAsOracle, information hub for superheroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAsOracle Context triple: [Barbara Gordon, roleAsOracle, information hub for superheroes]
-
A.
roleInGemini10
Indicates that an entity holds a specific role or position in the context of the Gemini 10 mission or project.
-
B.
roleInGemini3
Indicates that an entity holds a specific role or function within the Gemini 3 mission or project.
-
C.
roleInVega
Indicates that an entity holds a specific role or function within the Vega context (such as the Vega project, system, or framework).
-
D.
intelligenceRole
chosen
Indicates that an entity serves in an intelligence-related capacity or function (such as gathering, analyzing, or managing information) within a broader system or organization.
-
E.
roleWhen
Indicates a temporal relationship specifying the time or condition under which a particular role is held or applies.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f191620378819096362252c3b819b6 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.