Triple
T35691334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GR-75 medium transport |
E1031298
|
entity |
| Predicate | registryExample |
P98279
|
FINISHED |
| Object | Bright Hope |
—
|
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: Bright Hope | Statement: [GR-75 medium transport, registryExample, Bright Hope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registryExample Context triple: [GR-75 medium transport, registryExample, Bright Hope]
-
A.
registryType
Indicates the specific category or classification of a registry that an entity is associated with or recorded in.
-
B.
registrationOfNotableExample
chosen
Indicates that an entity serves as a notable or exemplary instance used to illustrate or document a particular registration.
-
C.
registryName
Indicates that an entity is identified or labeled by a specific name within a registry or registration system.
-
D.
registryURL
Indicates the web address where an entity’s official registration information is stored or can be accessed.
-
E.
registryFunction
Indicates a function that is responsible for registering or recording entities, configurations, or events within a registry or central management system.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.