Triple
T30682720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reason the Only Oracle of Man |
E781097
|
entity |
| Predicate | hasNotableAuthorOccupation |
P138401
|
FINISHED |
| Object | American revolutionary |
—
|
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: American revolutionary | Statement: [Reason the Only Oracle of Man, hasNotableAuthorOccupation, American revolutionary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAuthorOccupation Context triple: [Reason the Only Oracle of Man, hasNotableAuthorOccupation, American revolutionary]
-
A.
hasAuthorOccupationOfAuthor
chosen
Indicates that an author has a specific occupation or professional role.
-
B.
hasNotableAuthorWork
Indicates that an author is notably associated with creating a particular work.
-
C.
hasAuthorNotablePosition
Indicates that the author holds or has held a notable or distinguished position, role, or office.
-
D.
notableAuthorRole
Indicates that an entity holds a significant or distinguished role as an author in relation to another entity.
-
E.
hasNotableWriter
Indicates that an entity is associated with a writer who is recognized as significant or distinguished in some notable way.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
Created at: April 29, 2026, 8:33 p.m.