Triple
T37600674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhongsha Islands |
E935513
|
entity |
| Predicate | administeredByClaim |
P150290
|
FINISHED |
| Object | Sansha City |
—
|
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: Sansha City | Statement: [Zhongsha Islands, administeredByClaim, Sansha City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administeredByClaim Context triple: [Zhongsha Islands, administeredByClaim, Sansha City]
-
A.
administrativeControlClaimedBy
chosen
Indicates that an entity asserts or claims to hold administrative authority or control over another entity.
-
B.
administeredBy
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
-
C.
attributeClaim
Indicates that one entity asserts or specifies a particular attribute or property about another entity.
-
D.
administeredOnBehalfOf
Indicates that an action or service was carried out by one party acting in the interest of, or as a representative for, another party.
-
E.
recognizedAdministrationOf
Indicates that one entity has formally acknowledged and accepted another entity’s authority or control in an administrative capacity.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:18 p.m.