Triple
T33761084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnes G-function |
E865106
|
entity |
| Predicate | isEntireIn |
P140412
|
FINISHED |
| Object | z |
—
|
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: z | Statement: [Barnes G-function, isEntireIn, z]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEntireIn Context triple: [Barnes G-function, isEntireIn, z]
-
A.
isEntireFunction
chosen
Indicates that a function is defined and analytic over the entire complex plane (i.e., it is an entire function).
-
B.
runsEntirelyWithin
Indicates that one entity’s spatial or temporal extent is completely contained within the boundaries of another entity, without crossing or exceeding them.
-
C.
isExtensiveIn
Indicates that one entity is widespread, far-reaching, or broadly distributed within, across, or throughout another entity or domain.
-
D.
isDenseIn
Indicates that one set or subset is distributed so that its elements come arbitrarily close to every point of another set or space, leaving no gaps in that space.
-
E.
isOnlyPartOf
Indicates that an entity is a component exclusively of a specific whole and not of any other whole.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.