Triple
T25513362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icarus at the Edge of Time |
E639439
|
entity |
| Predicate | scienceConsultant |
P70912
|
FINISHED |
| Object | Brian Greene |
—
|
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: Brian Greene | Statement: [Icarus at the Edge of Time, scienceConsultant, Brian Greene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scienceConsultant Context triple: [Icarus at the Edge of Time, scienceConsultant, Brian Greene]
-
A.
scienceOfficer
Indicates that one entity serves in the role or capacity of a science officer in relation to another entity.
-
B.
scienceReturn
Indicates that an action or process yields scientific data, findings, or value as its outcome.
-
C.
scienceCase
Indicates a relationship where something serves as, constitutes, or provides justification as a scientific case or rationale for a study, hypothesis, or investigation.
-
D.
isScientific
Indicates that something pertains to or is based on systematic scientific methods, principles, or knowledge.
-
E.
scientificAuthority
chosen
Indicates that one entity is recognized as an expert or authoritative source in scientific matters relative to another entity or context.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f830a37c81909b3dae7a7ca10261 |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 2:54 p.m.