Triple
T29147474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRD |
E738810
|
entity |
| Predicate | administersAreaIncluding |
P110149
|
FINISHED |
| Object | Victoria |
—
|
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: Victoria | Statement: [CRD, administersAreaIncluding, Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administersAreaIncluding Context triple: [CRD, administersAreaIncluding, Victoria]
-
A.
administersFrom
Indicates that an action, service, or process is carried out or managed starting from a particular source, location, or authority.
-
B.
administersFor
Indicates that one entity provides or applies something (such as a treatment, service, or resource) on behalf of or for the benefit of another entity.
-
C.
regulatesArea
Indicates that one entity exercises control or governance over the spatial extent, scope, or domain of another entity.
-
D.
includesAreaOf
chosen
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
-
E.
regulatedArea
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 28, 2026, 11:40 a.m.