Triple

T15413297
Position Surface form Disambiguated ID Type / Status
Subject Guardian Bravo E368645 entity
Predicate jaegerType P18944 FINISHED
Object Mark-6 Jaeger E367931 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: Mark-6 Jaeger | Statement: [Guardian Bravo, jaegerType, Mark-6 Jaeger]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mark-6 Jaeger
Context triple: [Guardian Bravo, jaegerType, Mark-6 Jaeger]
  • A. Mark-6 Jaeger chosen
    The Mark-6 Jaeger is a highly advanced generation of giant humanoid combat robot from the Pacific Rim universe, featuring cutting-edge technology and enhanced performance over earlier Jaeger models.
  • B. 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.
  • C. 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.
  • D. Mark-3 Jaegers
    Mark-3 Jaegers are a generation of advanced giant combat mechs designed to battle Kaiju on the front lines in the Pacific Rim universe.
  • E. Jaeger
    Jaeger is an open-source, cloud-native distributed tracing system used to monitor and troubleshoot complex microservices-based applications.
  • 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_69d85a16c68c819099c1b547fbc87b32 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03ea7561481909b04e613e2352f82 completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff4c30ae4c8190b7a4739983963e86 completed May 9, 2026, 3:01 p.m.
Created at: April 10, 2026, 3:20 a.m.