Triple
T26474735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAMA 300 gravitational wave detector |
E665995
|
entity |
| Predicate | targetSignal |
P4618
|
FINISHED |
| Object | compact binary coalescences |
—
|
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: compact binary coalescences | Statement: [TAMA 300 gravitational wave detector, targetSignal, compact binary coalescences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetSignal Context triple: [TAMA 300 gravitational wave detector, targetSignal, compact binary coalescences]
-
A.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
B.
signalReach
Indicates the extent or range over which a signal can be effectively transmitted or received between entities.
-
C.
signalType
chosen
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
D.
targetsSystems
Indicates that an entity is directed at, attacks, or is intended to affect specific systems.
-
E.
targetsVector
Indicates that one entity is directed toward, aimed at, or focused on another entity represented as a vector (e.g., a direction or target position).
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 12:22 a.m.