Triple
T25626046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarke Papers |
E642432
|
entity |
| Predicate | occupationOfCollector |
P93726
|
FINISHED |
| Object | secretary to the Army |
—
|
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: secretary to the Army | Statement: [Clarke Papers, occupationOfCollector, secretary to the Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupationOfCollector Context triple: [Clarke Papers, occupationOfCollector, secretary to the Army]
-
A.
collectedBy
Indicates that one entity has gathered, acquired, or assembled another entity, typically as part of a collection or data-gathering process.
-
B.
patronOccupation
Indicates that one entity serves as the occupation or professional role held by a patron entity.
-
C.
significantCollector
Indicates that an entity plays an important or notable role in collecting items, works, or data related to another entity.
-
D.
occupationOf
Indicates that one entity holds or performs the job, role, or profession associated with another entity.
-
E.
occupationOfBearer
chosen
Indicates that a specified occupation or job role is held by the bearer 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 5:14 p.m.