Triple
T26643727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Schaack |
E668848
|
entity |
| Predicate | hasNotableFamilyPresenceIn |
P175215
|
FINISHED |
| Object | New York |
—
|
NE NERFINISHED |
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: New York | Statement: [Van Schaack, hasNotableFamilyPresenceIn, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFamilyPresenceIn Context triple: [Van Schaack, hasNotableFamilyPresenceIn, New York]
-
A.
hasNotableFamilyMembers
Indicates that an entity is related to one or more family members who are considered notable or significant in some context.
-
B.
hasNotableFamilyInField
Indicates that an individual has family members who are recognized or distinguished within a particular professional or academic field.
-
C.
hasOnScreenFamilyMember
Indicates that one entity appears on screen as a family member of another entity.
-
D.
hasFamilyFriend
Indicates that one entity has another entity as a friend who is connected through family ties or close familial relationships.
-
E.
hasMultiGenerationalPresenceIn
chosen
Indicates that an entity has maintained a continuous or recurring presence across multiple generations within a specified place or context.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: April 27, 2026, 2:30 a.m.