Triple
T35144214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pym van Dyne Foundation |
E1014775
|
entity |
| Predicate | usesLegacyTechnologyOf |
P45324
|
FINISHED |
| Object | Pym Particles |
—
|
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: Pym Particles | Statement: [Pym van Dyne Foundation, usesLegacyTechnologyOf, Pym Particles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLegacyTechnologyOf Context triple: [Pym van Dyne Foundation, usesLegacyTechnologyOf, Pym Particles]
-
A.
usesLegacyOf
Indicates that one entity makes use of, builds upon, or derives benefit from the historical work, reputation, or established influence of another entity.
-
B.
isConsideredLegacy
Indicates that something is regarded as outdated or superseded, typically maintained only for backward compatibility or historical reasons.
-
C.
hasLegacy
Indicates that an entity leaves behind a lasting impact, influence, or inheritance that continues to exist or be recognized over time.
-
D.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
-
E.
technologyLegacy
chosen
Indicates that one entity has inherited, retained, or is influenced by the past technologies, systems, or technical decisions associated with another entity.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.