Triple
T13203562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CQD |
E314299
|
entity |
| Predicate | replacedInDomain |
P108496
|
FINISHED |
| Object | international maritime distress signaling |
—
|
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: international maritime distress signaling | Statement: [CQD, replacedInDomain, international maritime distress signaling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedInDomain Context triple: [CQD, replacedInDomain, international maritime distress signaling]
-
A.
replacedInCountry
Indicates that one entity has been substituted or superseded by another within the context or jurisdiction of a specific country.
-
B.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
C.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
-
D.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
E.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9961a48190a1157df47f59b7af |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:17 p.m.