Triple
T8422078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | López family line |
E198880
|
entity |
| Predicate | hasNotableFieldOfDescendant |
P82096
|
FINISHED |
| Object | art |
—
|
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: art | Statement: [López family line, hasNotableFieldOfDescendant, art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFieldOfDescendant Context triple: [López family line, hasNotableFieldOfDescendant, art]
-
A.
hasNotableDescendant
Indicates that an entity has at least one descendant who is recognized as notable or significant in some context.
-
B.
hasNotableParent
Indicates that an entity has a parent who is distinguished, prominent, or otherwise notable.
-
C.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
D.
hasNotableSuccessorType
Indicates that an entity has a successor whose type or category is considered notably significant or distinguished in relation to it.
-
E.
hasNotableRelativeGroup
Indicates that an entity is associated with a group of relatives who are notable or significant in some recognized way.
- 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_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. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:06 p.m.