Triple
T70686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fisherman’s Wharf |
E1414
|
entity |
| Predicate | historicalCommunity |
P3032
|
FINISHED |
| Object | Italian-American fishermen |
—
|
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: Italian-American fishermen | Statement: [Fisherman’s Wharf, historicalCommunity, Italian-American fishermen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCommunity Context triple: [Fisherman’s Wharf, historicalCommunity, Italian-American fishermen]
-
A.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
B.
historicallyInhabitedBy
chosen
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
C.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
D.
historicalAssessment
Indicates an evaluation or judgment of something based on its historical context, significance, or development over time.
-
E.
notableCommunity
Indicates that an entity is a particularly prominent or significant member of a given community.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24eaa0df88190add55579b2b9fd02 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.