Triple
T36958565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Railgun (Quake) |
E914248
|
entity |
| Predicate | notableCommunityTerm |
P205664
|
FINISHED |
| Object | rail shot |
—
|
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: rail shot | Statement: [Railgun (Quake), notableCommunityTerm, rail shot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCommunityTerm Context triple: [Railgun (Quake), notableCommunityTerm, rail shot]
-
A.
notableCommunity
Indicates that an entity is a particularly prominent or significant member of a given community.
-
B.
notableUserCommunity
Indicates that a user has a significant or distinguished presence, role, or recognition within a particular community.
-
C.
eraOfNotableCommunity
Indicates that a particular time period is recognized as a notable or defining era for a specific community.
-
D.
notableCommunityAffected
Indicates that a particular community of notable significance is directly impacted or influenced by the subject.
-
E.
celebratedByCommunity
Indicates that an event, person, or achievement is honored, recognized, or joyfully acknowledged by a community.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.