Triple
T10057594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | zu-yong-diao system |
E208899
|
entity |
| Predicate | collectionUnit |
P79650
|
FINISHED |
| Object | prefectures |
—
|
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: prefectures | Statement: [zu-yong-diao system, collectionUnit, prefectures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionUnit Context triple: [zu-yong-diao system, collectionUnit, prefectures]
-
A.
collectionRepository
Indicates a relationship where a repository is responsible for storing, managing, or providing access to a collection.
-
B.
collectionFormed
Indicates that multiple items or entities have been gathered and organized together into a defined collection.
-
C.
collectionKind
chosen
Indicates the type or category of collection to which an entity or group of entities belongs.
-
D.
collectionBy
Indicates that one entity is the collector or curator responsible for assembling, managing, or owning a particular collection of items represented by another entity.
-
E.
collectionRole
Indicates the specific function, responsibility, or position an entity holds within a collection or grouped set of items.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfaf7700819084dedf7b63e789c1 |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.