Triple
T13226459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hague Express Database |
E314891
|
entity |
| Predicate | supportsSearchBy |
P106401
|
FINISHED |
| Object | international registration number |
—
|
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: international registration number | Statement: [Hague Express Database, supportsSearchBy, international registration number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSearchBy Context triple: [Hague Express Database, supportsSearchBy, international registration number]
-
A.
isSearchable
Indicates that the referenced entity can be discovered or retrieved through a search operation or query.
-
B.
hasSearchField
chosen
Indicates that an entity includes or is associated with a search input field that can be used to query or filter information.
-
C.
supportsFinding
Indicates that one entity provides the capability or functionality needed to perform, enable, or carry out a particular finding operation on another entity or resource.
-
D.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
E.
searchesVia
Indicates that an entity performs a search by means of, or using, a specified tool, method, or channel.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d3232d48190a3c792b025c596a6 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:20 p.m.