Triple
T33629241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K2K experiment |
E861502
|
entity |
| Predicate | countryOfFarDetector |
P50453
|
FINISHED |
| Object | Japan |
—
|
NE NERFINISHED |
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: Japan | Statement: [K2K experiment, countryOfFarDetector, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfFarDetector Context triple: [K2K experiment, countryOfFarDetector, Japan]
-
A.
hasFarDetector
Indicates that an entity is equipped with or associated with a detector positioned at a relatively large distance from a reference point or source.
-
B.
farDetectorCountry
chosen
Indicates that one entity is the country in which the far (more distant) detector associated with another entity is located.
-
C.
radarOriginCountry
Indicates the country from which a radar system originates or is produced.
-
D.
hasFarDetectorFunction
Indicates that an entity possesses a function or capability specifically related to detecting objects, signals, or phenomena at a long or extended distance.
-
E.
farDetectorLocation
Indicates that one entity is located at or corresponds to the position of a far (distant) detector relative to another reference point or system.
- F. None of above.
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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00c07b302081908bf9755f8fdbc36e |
completed | May 10, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_6a00bfffb168819084b65804d601896d |
completed | May 10, 2026, 5:27 p.m. |
Created at: May 1, 2026, 1:41 a.m.