Triple
T31712184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San DiFrangeles |
E809355
|
entity |
| Predicate | hasElementFrom |
P11236
|
FINISHED |
| Object | San Diego culture |
—
|
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: San Diego culture | Statement: [San DiFrangeles, hasElementFrom, San Diego culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElementFrom Context triple: [San DiFrangeles, hasElementFrom, San Diego culture]
-
A.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
-
B.
includesElement
chosen
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
C.
hasElementCondition
Indicates that an entity is associated with a specific condition or set of conditions applied to one of its elements or components.
-
D.
hasBruteElement
Indicates that an entity possesses or is associated with a raw, force-based, or brute-type elemental property.
-
E.
hasFrameElement
Indicates that a frame (or structured conceptual scenario) includes or is associated with a specific frame element (a participant, role, or component within that frame).
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 30, 2026, 11:16 p.m.