Triple
T34255850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global North |
E878874
|
entity |
| Predicate | isNotStrictlyDefinedBy |
P3573
|
FINISHED |
| Object | geographic latitude |
—
|
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: geographic latitude | Statement: [Global North, isNotStrictlyDefinedBy, geographic latitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotStrictlyDefinedBy Context triple: [Global North, isNotStrictlyDefinedBy, geographic latitude]
-
A.
partlyDefinedBy
chosen
Indicates that one entity’s nature, role, or characteristics are only partially determined or specified by another entity.
-
B.
doesNotDefine
Indicates that one entity does not provide a definition, specification, or determining description for another entity.
-
C.
wasDefinedBy
Indicates that something was formally specified, described, or established by a particular agent, source, or defining entity.
-
D.
notEnforcedBy
Indicates that a rule, policy, or obligation is not upheld, imposed, or carried out by the referenced enforcing entity.
-
E.
isCommonlyDefinedBy
Indicates that something is typically or most frequently characterized, specified, or described by a particular definition, property, or set of criteria.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.