Triple
T22284157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuchow |
E550813
|
entity |
| Predicate | topicalDomain |
P53727
|
FINISHED |
| Object | geography |
—
|
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: geography | Statement: [Fuchow, topicalDomain, geography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topicalDomain Context triple: [Fuchow, topicalDomain, geography]
-
A.
territorialDomain
Indicates that one entity has territorial authority, control, or jurisdiction over a geographic area or domain associated with another entity.
-
B.
domainOfq
Indicates that a given entity serves as the domain (set of permissible inputs or arguments) for the quantity or relation denoted by q.
-
C.
partOfDomain
Indicates that one entity belongs to, is included within, or is a constituent part of the scope or domain defined by another entity.
-
D.
domainFocus
chosen
Indicates that one entity is the primary topical or subject-matter focus within the conceptual or informational domain defined by another entity.
-
E.
publicDomain
Indicates that a work or resource is not protected by intellectual property rights and is freely available for anyone to use, copy, modify, and distribute without restriction.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15605a8448190906a0ab9ffa4260b |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.