Triple
T31552781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swainson, 1839 |
E805048
|
entity |
| Predicate | geographicRelevance |
P181078
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [Swainson, 1839, geographicRelevance, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicRelevance Context triple: [Swainson, 1839, geographicRelevance, global]
-
A.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
B.
relevanceToCity
Indicates that something has a meaningful connection, impact, or applicability to a particular city.
-
C.
isGeographicallySpecific
Indicates that something is limited to or uniquely associated with a particular geographic location or area.
-
D.
geographyBehavior
Indicates how an entity behaves, functions, or interacts in relation to its geographic context or location.
-
E.
geographicCriterion
Indicates that the relationship or selection is determined based on geographic factors, such as location, region, or spatial boundaries.
- F. None of above. chosen
Provenance (4 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: April 30, 2026, 10:11 p.m.