Triple
T26657400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominic Greene |
E666545
|
entity |
| Predicate | roleInQuantum |
P34669
|
FINISHED |
| Object | high-ranking member |
—
|
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: high-ranking member | Statement: [Dominic Greene, roleInQuantum, high-ranking member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInQuantum Context triple: [Dominic Greene, roleInQuantum, high-ranking member]
-
A.
quantumMechanicalRole
Indicates the specific function or behavior an entity has within a quantum mechanical process, interaction, or system.
-
B.
roleInQuantumGravity
chosen
Indicates that an entity has a specific function, status, or contribution within the theoretical framework or research program of quantum gravity.
-
C.
roleInResearch
Indicates that an entity participates in a research activity with a specified function, position, or responsibility within that research.
-
D.
roleInGemini3
Indicates that an entity holds a specific role or function within the Gemini 3 mission or project.
-
E.
roleInFinance
Indicates that an entity holds a specific function, responsibility, or position within a financial context, system, or transaction.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 27, 2026, 2:35 a.m.