Triple
T15386627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vortex Cannon |
E367932
|
entity |
| Predicate | usedBy |
P260
|
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: [Vortex Cannon, usedBy, Jaegers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jaegers Context triple: [Vortex Cannon, usedBy, 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-6 Jaeger
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.
-
E.
Mahikari
Mahikari is a Japanese new religious movement known for its emphasis on spiritual purification through the transmission of divine light.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e74ff70819094c1a85f51d6e228 |
completed | April 16, 2026, 1:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff1a6d35148190aa4dc0c2a7bf849d |
completed | May 9, 2026, 11:28 a.m. |
Created at: April 10, 2026, 3:19 a.m.