Triple
T1048403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Wall Station |
E22635
|
entity |
| Predicate | hasCommunication |
P3332
|
FINISHED |
| Object | satellite link to mainland China |
—
|
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: satellite link to mainland China | Statement: [Great Wall Station, hasCommunication, satellite link to mainland China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunication Context triple: [Great Wall Station, hasCommunication, satellite link to mainland China]
-
A.
hasCommunicationFrequency
Indicates how often communication occurs between the related entities.
-
B.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
C.
communicationMode
chosen
Indicates the method or channel through which communication between entities is carried out.
-
D.
communicationStatus
Indicates the current state or condition of a communication process or exchange between entities (e.g., pending, active, failed, completed).
-
E.
correspondedWith
Indicates that two entities engaged in mutual communication, typically by exchanging messages or letters over a period of time.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.