Triple
T28343776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KAGRA gravitational-wave detector |
E717889
|
entity |
| Predicate | partnerDetector |
P63242
|
FINISHED |
| Object | LIGO |
—
|
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: LIGO | Statement: [KAGRA gravitational-wave detector, partnerDetector, LIGO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerDetector Context triple: [KAGRA gravitational-wave detector, partnerDetector, LIGO]
-
A.
partnerInDiscovery
Indicates that two or more entities collaborated as partners in making a particular discovery.
-
B.
partnerInOrganizationWith
chosen
Indicates that two entities are associated as partners within the same organization or organizational context.
-
C.
intendedPartner
Indicates that one entity is designated or expected to be the future or planned partner (e.g., romantic, marital, or business) of another entity.
-
D.
partnerCount
Indicates the number of partners associated with a given entity in the relationship.
-
E.
partnerNation
Indicates that one entity is recognized as a collaborating or allied nation in relation to another entity.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 12:41 a.m.