Triple
T5331529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peach Capital of Alabama |
E123320
|
entity |
| Predicate | denotesSpecialization |
P21480
|
FINISHED |
| Object | peach cultivation |
—
|
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: peach cultivation | Statement: [Peach Capital of Alabama, denotesSpecialization, peach cultivation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesSpecialization Context triple: [Peach Capital of Alabama, denotesSpecialization, peach cultivation]
-
A.
positionSpecialization
Indicates that one position is a more specialized or focused variant of another, broader position.
-
B.
hasSpecialist
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
-
C.
uniformSpecialty
Indicates that multiple entities share the same specific specialty, expertise, or area of focus.
-
D.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
E.
regionSpecialization
chosen
Indicates that a region is designated or recognized as being particularly focused on, adapted to, or specialized in a specific function, activity, or domain.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85aab0308190990626cbc9da3e21 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.