Triple
T3581501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimrod MR2 |
E75808
|
entity |
| Predicate | hasMAD |
P49861
|
FINISHED |
| Object | tail-mounted magnetic anomaly detector |
—
|
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: tail-mounted magnetic anomaly detector | Statement: [Nimrod MR2, hasMAD, tail-mounted magnetic anomaly detector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMAD Context triple: [Nimrod MR2, hasMAD, tail-mounted magnetic anomaly detector]
-
A.
hasMP
Indicates that an entity is represented by, or associated with, a specific Member of Parliament (MP).
-
B.
hasMIC
Indicates that an entity has a specified Minimum Inhibitory Concentration (MIC) value in relation to an antimicrobial agent.
-
C.
hasMace
Indicates that one entity possesses, carries, or is equipped with a mace.
-
D.
hasMCR
Indicates a relationship where an entity is associated with, or possesses, a specific MCR (e.g., a defined minimum capital requirement or similarly named regulatory/technical measure).
-
E.
hasPar
Indicates a relationship where one entity has another entity as its parent.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc101738c81908d38987f8fa291ef |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:21 p.m.