Triple
T31424524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Register of Historic Vessels |
E801622
|
entity |
| Predicate | maintainsOnlineDatabase |
P65134
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [National Register of Historic Vessels, maintainsOnlineDatabase, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsOnlineDatabase Context triple: [National Register of Historic Vessels, maintainsOnlineDatabase, true]
-
A.
hasOnlineDatabases
chosen
Indicates that an entity maintains or provides access to one or more databases that are available online.
-
B.
databaseMaintainedBy
Indicates that a particular database is operated, managed, or kept up-to-date by a specified agent or organization.
-
C.
dataMaintained
Indicates that one entity is responsible for preserving, storing, or keeping another entity’s data up to date and accessible over time.
-
D.
supportsDatabaseConnectivity
Indicates that an entity provides the capability to establish and maintain connections to a database system.
-
E.
statusInDatabases
Indicates the current state or condition an entity has within one or more database systems.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 30, 2026, 8:51 p.m.