Triple
T17310659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novacene epoch |
E420285
|
entity |
| Predicate | dominantForce |
P19407
|
FINISHED |
| Object | artificial systems |
—
|
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: artificial systems | Statement: [Novacene epoch, dominantForce, artificial systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantForce Context triple: [Novacene epoch, dominantForce, artificial systems]
-
A.
primaryForce
chosen
Indicates that one entity serves as the main or dominant force acting upon, influencing, or driving another entity or process.
-
B.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
C.
typeOfForcesDirected
Indicates that certain forces are oriented or directed toward a particular target, direction, or reference.
-
D.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
E.
forces
Indicates that one entity compels or obliges another entity to perform an action or be in a certain state, typically against the latter’s will or without full freedom of choice.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399837b08190b7cf74201b3cb013 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.