Triple
T8422071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | López family line |
E198880
|
entity |
| Predicate | isDocumentedThrough |
P69655
|
FINISHED |
| Object | maternal surname López |
—
|
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: maternal surname López | Statement: [López family line, isDocumentedThrough, maternal surname López]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDocumentedThrough Context triple: [López family line, isDocumentedThrough, maternal surname López]
-
A.
documentedThrough
chosen
Indicates that something is recorded, evidenced, or made known by means of a specific document or documentation process.
-
B.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
C.
hasDocumentationAt
Indicates that something is documented or described in a specific document, file, or location.
-
D.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
E.
hasDocumentationStatus
Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb859e22f88190a61e7dd6537644b0 |
completed | March 31, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.