Triple
T31588393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eric Pålsson Mullica |
E806020
|
entity |
| Predicate | hasHomestead |
P104753
|
FINISHED |
| Object | Mullica family homestead in New Jersey |
—
|
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: Mullica family homestead in New Jersey | Statement: [Eric Pålsson Mullica, hasHomestead, Mullica family homestead in New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomestead Context triple: [Eric Pålsson Mullica, hasHomestead, Mullica family homestead in New Jersey]
-
A.
hasHome
chosen
Indicates that an entity possesses or is associated with a place where it lives or is based.
-
B.
hasHomeland
Indicates that an entity considers or recognizes a particular place or region as its homeland or place of origin.
-
C.
hasOriginalHomesteadDestroyed
Indicates that an entity’s original homestead or primary dwelling was destroyed.
-
D.
hasTollHouse
Indicates that an entity possesses, includes, or is associated with a toll house (a building or facility where tolls are collected).
-
E.
hasGatehouse
Indicates that one entity possesses or includes a gatehouse as part of its structure or property.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 30, 2026, 10:27 p.m.