Triple
T4285348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Locust Point |
E97253
|
entity |
| Predicate | wasMajorEntryPointFor |
P26211
|
FINISHED |
| Object | European immigrants to Baltimore |
—
|
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: European immigrants to Baltimore | Statement: [Locust Point, wasMajorEntryPointFor, European immigrants to Baltimore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMajorEntryPointFor Context triple: [Locust Point, wasMajorEntryPointFor, European immigrants to Baltimore]
-
A.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
B.
entryPointFor
Indicates that one entity serves as the access or starting location through which another entity is entered, initiated, or reached.
-
C.
isMajorBaseIn
Indicates that a location serves as a primary or central base of operations within a specified area or organization.
-
D.
hasMajorComponent
Indicates that one entity includes another entity as a primary or most significant component or part.
-
E.
isMajorAccessPointFor
chosen
Indicates that something serves as a primary or significant entry or connection point for accessing another entity or system.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3505bff588190919a4ef547f607c2 |
completed | March 12, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.