Triple
T23593009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack S. Josey |
E582532
|
entity |
| Predicate | fieldOfSupport |
P152841
|
FINISHED |
| Object | science |
—
|
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: science | Statement: [Jack S. Josey, fieldOfSupport, science]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfSupport Context triple: [Jack S. Josey, fieldOfSupport, science]
-
A.
fieldOfOperation
Indicates the domain, area, or scope within which an entity operates or carries out its primary activities.
-
B.
militarySupportActivity
Indicates an action where one entity provides military-related assistance, resources, or operational support to another.
-
C.
militarySupportTheme
Indicates that one entity provides, requests, or is associated with military assistance, backing, or involvement in relation to another entity or situation.
-
D.
fieldOfRecognition
Indicates the domain, discipline, or area in which an entity is formally acknowledged, honored, or recognized.
-
E.
missionField
Indicates a relationship where an entity’s work, activity, or purpose is directed toward a particular area, domain, or target context as its mission focus.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b08befcc819095e0e6052e6fe787 |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:42 p.m.