Triple
T17409164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life and Letters of Thomas Henry Huxley |
E423300
|
entity |
| Predicate | editorGender |
P127354
|
FINISHED |
| Object | male |
—
|
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: male | Statement: [Life and Letters of Thomas Henry Huxley, editorGender, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorGender Context triple: [Life and Letters of Thomas Henry Huxley, editorGender, male]
-
A.
namedEditorInChief
Indicates that one entity has been designated to serve in the role of editor-in-chief for another entity, such as a publication or organization.
-
B.
editorName
Indicates the relationship that specifies the name of an editor associated with a given entity.
-
C.
editorOfWork
Indicates that one entity serves as the editor responsible for preparing, revising, or overseeing the content of a particular work.
-
D.
editedBy
Indicates that one entity has revised, modified, or otherwise made editorial changes to another entity.
-
E.
editorialRole
Indicates that one entity holds an editorial position or responsibility in relation to another entity, such as a publication, work, or organization.
- F. None of above. chosen
Provenance (4 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43b0990f48190b62d73087ae1a0d7 |
completed | April 19, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:46 a.m.