Triple
T6906537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meitnerium |
E159825
|
entity |
| Predicate | projectileInDiscovery |
P28555
|
FINISHED |
| Object | iron-58 |
—
|
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: iron-58 | Statement: [Meitnerium, projectileInDiscovery, iron-58]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectileInDiscovery Context triple: [Meitnerium, projectileInDiscovery, iron-58]
-
A.
involvesProjectile
Indicates that the action or event includes the use, presence, or motion of a projectile as a key component of the interaction between entities.
-
B.
catapults
Indicates launching or forcefully propelling one entity through the air toward another location or target.
-
C.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
D.
discoveredWith
chosen
Indicates that one entity was found, detected, or identified using another entity as the means, tool, method, or accompanying context of discovery.
-
E.
catapultOrigin
Indicates the original source or starting point from which something is launched or propelled, as by a catapult.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d98c3ab08190a1830c45578056ac |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.