Triple
T38473909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contee |
E915494
|
entity |
| Predicate | occursInRecordsType |
P2554
|
FINISHED |
| Object | genealogical records |
—
|
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: genealogical records | Statement: [Contee, occursInRecordsType, genealogical records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursInRecordsType Context triple: [Contee, occursInRecordsType, genealogical records]
-
A.
containsRecord
Indicates that one entity holds, includes, or stores a particular record within it.
-
B.
hasRecordType
chosen
Indicates that an entity is associated with or classified under a specific type or category of record.
-
C.
occursFor
Indicates that an event, process, or condition takes place in relation to, or on behalf of, a particular entity or context.
-
D.
isRecord
Indicates that one entity functions as an official or authoritative record of another entity or of some information.
-
E.
occursInProgram
Indicates that an event, action, or element takes place within or is contained in a specific program.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.