Triple
T23740857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan A (Interstellar) |
E586666
|
entity |
| Predicate | coreMethod |
P859
|
FINISHED |
| Object | completion of a unified gravity equation |
—
|
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: completion of a unified gravity equation | Statement: [Plan A (Interstellar), coreMethod, completion of a unified gravity equation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreMethod Context triple: [Plan A (Interstellar), coreMethod, completion of a unified gravity equation]
-
A.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
B.
coreModule
Indicates that something functions as a primary or foundational module within a larger system or structure.
-
C.
coreAction
Indicates the primary or central action that defines the main relationship or event occurring between the involved entities.
-
D.
compilerMethod
Indicates that a method is used by or generated for the compiler as part of the code compilation process.
-
E.
secondaryMethod
Indicates that an entity serves as an additional or backup method used alongside or after a primary method in performing an action or achieving a result.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad61d908190a0a8493bbba95d49 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:11 p.m.