Triple
T38116872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weapon XIII |
E951813
|
entity |
| Predicate | programmedTrait |
P191068
|
FINISHED |
| Object | artificial personality |
—
|
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 personality | Statement: [Weapon XIII, programmedTrait, artificial personality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmedTrait Context triple: [Weapon XIII, programmedTrait, artificial personality]
-
A.
programmingTrait
Indicates a characteristic, quality, or attribute specifically related to programming behavior, style, or capability associated with an entity.
-
B.
developedTrait
Indicates that an entity has acquired or evolved a particular characteristic, quality, or feature over time.
-
C.
programmedVia
Indicates that one entity is created, configured, or made to operate through the use of another entity as its programming method, tool, or medium.
-
D.
breedingTrait
Indicates that an entity possesses a heritable characteristic that is relevant or targeted in a breeding process or program.
-
E.
initialTrait
Indicates that a particular trait or characteristic is present in an entity at the beginning of a process, state, or time period.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: May 3, 2026, 4:21 p.m.