Triple
T35828010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Pentangeli |
E1035705
|
entity |
| Predicate | operatesTerritory |
P126730
|
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: [Frank Pentangeli, operatesTerritory, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesTerritory Context triple: [Frank Pentangeli, operatesTerritory, New York]
-
A.
operatesFromTerritory
chosen
Indicates that an entity conducts its activities or operations based out of, or primarily within, a specified territory.
-
B.
operatesToRegion
Indicates that an agent conducts operations or provides services directed toward or within a specified region.
-
C.
operatesInTerritoriesOutside
Indicates that an entity conducts activities or maintains operations in geographic areas beyond its primary or home territories.
-
D.
overseesTerritoryType
Indicates that an entity has supervisory or administrative responsibility over a specified type of territory.
-
E.
operatedInRegion
Indicates that an entity conducted operations or activities within a specified geographic region.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0186cde2fc819080d7c06503dcc479 |
completed | May 11, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_6a0183ff6d34819080c8ad7c11611a36 |
completed | May 11, 2026, 7:23 a.m. |
Created at: May 3, 2026, 4:06 p.m.