Triple
T16547365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Breach |
E401975
|
entity |
| Predicate | opposedBy |
P437
|
FINISHED |
| Object | Jaegers |
E74820
|
NE 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: Jaegers | Statement: [The Breach, opposedBy, Jaegers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jaegers Context triple: [The Breach, opposedBy, Jaegers]
-
A.
Jaegers
chosen
Jaegers are giant humanoid combat robots piloted by humans to battle monstrous kaiju in the Pacific Rim universe.
-
B.
Jaeger
Jaeger is an open-source, cloud-native distributed tracing system used to monitor and troubleshoot complex microservices-based applications.
-
C.
Jaeger
Jaegers are giant humanoid combat robots piloted by humans to battle monstrous Kaiju in the Pacific Rim universe.
-
D.
Mark-4 Jaegers
Mark-4 Jaegers are a later-generation class of giant humanoid combat mechs in the Pacific Rim universe, designed with advanced technology and improved combat capabilities to battle Kaiju on the front lines.
-
E.
Mark-5 Jaegers
Mark-5 Jaegers are the most advanced generation of giant human-piloted combat mechs in the Pacific Rim universe, designed as cutting-edge war machines for battling Kaiju.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fbe3fb48190bad143b50dc73c7e |
completed | April 18, 2026, 9:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0067b4f6448190812632ab9023b665 |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:15 a.m.