Triple
T32013918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apex Cybernetics |
E817481
|
entity |
| Predicate | developedTechnologyAgainst |
P184873
|
FINISHED |
| Object | Titans |
—
|
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: Titans | Statement: [Apex Cybernetics, developedTechnologyAgainst, Titans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedTechnologyAgainst Context triple: [Apex Cybernetics, developedTechnologyAgainst, Titans]
-
A.
opposedTechnology
Indicates that one entity actively resists, rejects, or works against the use, adoption, or development of a particular technology associated with another entity.
-
B.
developsTechnologyFor
Indicates that one entity creates, improves, or engineers technology specifically intended to be used by or to benefit another entity.
-
C.
inUniverseTechnologyDeveloped
Indicates that a specific technology has been created or developed within the context of a particular fictional or defined universe.
-
D.
technologyCounterpartOf
Indicates a relationship where one technology serves as an equivalent, alternative, or corresponding counterpart to another technology.
-
E.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: May 1, 2026, 12:15 a.m.