Triple
T36953928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rise of Rome |
E914141
|
entity |
| Predicate | addsTechnology |
P186783
|
FINISHED |
| Object | new technologies for Iron Age |
—
|
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: new technologies for Iron Age | Statement: [The Rise of Rome, addsTechnology, new technologies for Iron Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsTechnology Context triple: [The Rise of Rome, addsTechnology, new technologies for Iron Age]
-
A.
enablesTechnology
Indicates that one entity makes it possible for another entity, system, or process to function through the use or provision of a particular technology.
-
B.
appliesTechnologyIn
Indicates that an entity makes use of or implements a particular technology within a specific context or activity.
-
C.
combinesTechnologyFrom
Indicates that one entity integrates or merges technological components, methods, or features originating from another entity.
-
D.
associatedWithTechnology
Indicates a relationship where an entity is connected to, involved with, or utilizes a particular technology.
-
E.
acquiredTechnologyFrom
Indicates that one entity obtained or gained access to a technology from another entity.
- F. None of above. chosen
Provenance (4 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.