Triple
T16747715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CNKI |
E406997
|
entity |
| Predicate | alternativeDomain |
P31023
|
FINISHED |
| Object | https://oversea.cnki.net |
—
|
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: https://oversea.cnki.net | Statement: [CNKI, alternativeDomain, https://oversea.cnki.net]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeDomain Context triple: [CNKI, alternativeDomain, https://oversea.cnki.net]
-
A.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
-
B.
secondaryDomain
Indicates that one domain functions as a secondary or auxiliary domain in relation to a primary domain.
-
C.
supportsCustomDomain
chosen
Indicates that an entity provides the capability to use or configure a custom domain name instead of a default or system-assigned domain.
-
D.
formerDomain
Indicates that one entity was previously the domain or area of control, influence, or ownership of another entity, but no longer is.
-
E.
replacedInDomain
Indicates that one entity has been superseded or substituted by another within a specific domain or contextual scope.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2439848190a86a5bfc0702e2fe |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.