Triple
T32214221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbrand base |
E822884
|
entity |
| Predicate | roleInSemantics |
P108488
|
FINISHED |
| Object | serves as domain of discourse for Herbrand interpretations |
—
|
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: serves as domain of discourse for Herbrand interpretations | Statement: [Herbrand base, roleInSemantics, serves as domain of discourse for Herbrand interpretations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSemantics Context triple: [Herbrand base, roleInSemantics, serves as domain of discourse for Herbrand interpretations]
-
A.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
B.
roleInGemini10
Indicates that an entity holds a specific role or position in the context of the Gemini 10 mission or project.
-
C.
roleOfPerson
Indicates that a specific role, function, or position is assigned to or held by a particular person.
-
D.
roleInGemini3
Indicates that an entity holds a specific role or function within the Gemini 3 mission or project.
-
E.
roleInMetadata
chosen
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: May 1, 2026, 12:37 a.m.