Triple
T21314542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicholas Roosevelt |
E525430
|
entity |
| Predicate | hasCollaborationSubject |
P97010
|
FINISHED |
| Object | steam-powered navigation |
—
|
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: steam-powered navigation | Statement: [Nicholas Roosevelt, hasCollaborationSubject, steam-powered navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollaborationSubject Context triple: [Nicholas Roosevelt, hasCollaborationSubject, steam-powered navigation]
-
A.
hasCollaborationTopic
chosen
Indicates that two or more entities are engaged in a collaboration focused on a specified topic or subject area.
-
B.
containsCollaboration
Indicates that one entity includes or involves a collaborative relationship or joint activity with another entity.
-
C.
hasCollectionSubject
Indicates that a collection is about or thematically centered on a particular subject.
-
D.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
-
E.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dce6b4081909841ac0440fca5e4 |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:28 p.m.