Triple
T3282675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O Captain! My Captain! |
E68907
|
entity |
| Predicate | addedToCollection |
P1925
|
FINISHED |
| Object | 1867 edition of Leaves of Grass |
—
|
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: 1867 edition of Leaves of Grass | Statement: [O Captain! My Captain!, addedToCollection, 1867 edition of Leaves of Grass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedToCollection Context triple: [O Captain! My Captain!, addedToCollection, 1867 edition of Leaves of Grass]
-
A.
addedTo
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
B.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
C.
partOfCollection
chosen
Indicates that an entity belongs to, or is included within, a larger collection or set.
-
D.
knownForCollectionOf
Indicates that one entity is recognized or notable specifically for its collection or assemblage of another type of entity.
-
E.
hasCollectionFrom
Indicates that an entity possesses or maintains a collection that originates from, or is sourced from, another specified entity.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0345d448190a1f936abe7748e33 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.