Triple
T3685245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swords and Plowshares |
E78207
|
entity |
| Predicate | hasAuthorRank |
P11443
|
FINISHED |
| Object | General |
—
|
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: General | Statement: [Swords and Plowshares, hasAuthorRank, General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorRank Context triple: [Swords and Plowshares, hasAuthorRank, General]
-
A.
hasAuthor
Indicates that an entity is written or created by a specific author.
-
B.
hasAcademicRank
Indicates that an entity holds a specific academic rank or title within an educational or research institution.
-
C.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
D.
hasRankCategory
chosen
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
E.
hasAuthorPublished
Indicates that a specific author has produced and made publicly available at least one work, such as a book, article, or paper.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4c49b408190bc800bcf9745fe4f |
completed | March 8, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.