Triple
T31716776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auxiliary General Oceanographic Research |
E809472
|
entity |
| Predicate | hasPrefixPattern |
P87534
|
FINISHED |
| Object | AGOR-## |
—
|
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: AGOR-## | Statement: [Auxiliary General Oceanographic Research, hasPrefixPattern, AGOR-##]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrefixPattern Context triple: [Auxiliary General Oceanographic Research, hasPrefixPattern, AGOR-##]
-
A.
hasPrefix
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
B.
hasPattern
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
C.
hasPreMessagePattern
Indicates that an entity is associated with a specific pattern or structure that must appear in a message before a given point or event.
-
D.
hasStartPattern
chosen
Indicates that something begins with, or is characterized at its outset by, a specified pattern.
-
E.
hasExpansionPattern
Indicates that an entity follows or is associated with a specific pattern or manner of expansion.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a007ef69f5c8190be6fb89e918d30fa |
completed | May 10, 2026, 12:49 p.m. |
| PD | Predicate disambiguation | batch_6a007e4060448190ad7420b07c1fe219 |
completed | May 10, 2026, 12:46 p.m. |
Created at: April 30, 2026, 11:17 p.m.