Triple
T38576682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smythe family |
E929423
|
entity |
| Predicate | hasHistoricAssociationSince |
P42477
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Smythe family, hasHistoricAssociationSince, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricAssociationSince Context triple: [Smythe family, hasHistoricAssociationSince, 17th century]
-
A.
hasHistoricManagerAssociation
Indicates a past managerial relationship between entities that no longer reflects the current management status.
-
B.
hasHistorySince
chosen
Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
-
C.
reflectsHistoricalAssociationWith
Indicates a relationship in which one entity shows or embodies a connection, link, or relevance to another entity based on past events, contexts, or historical ties.
-
D.
hasHistoryWith
Indicates that there is a prior relationship, interaction, or shared past between the entities.
-
E.
hasHistoricVicinity
Indicates that one entity is located near or within an area of historical significance associated with another 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:32 p.m.