Triple
T32085090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nethuns |
E819417
|
entity |
| Predicate | laterIdentifiedAs |
P144948
|
FINISHED |
| Object | Neptune in Roman context |
—
|
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: Neptune in Roman context | Statement: [Nethuns, laterIdentifiedAs, Neptune in Roman context]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterIdentifiedAs Context triple: [Nethuns, laterIdentifiedAs, Neptune in Roman context]
-
A.
laterDescribedAs
Indicates that an entity is referred to or characterized by a particular description or label at a later time.
-
B.
laterNamed
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
-
C.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
-
D.
laterBecameKnownAs
chosen
Indicates that an entity was previously known by one name or identity and, at a later time, came to be known by a different name or identity.
-
E.
candidateIdentifiedAs
Indicates that a particular individual or option has been recognized or designated as the specific candidate in question.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 1, 2026, 12:24 a.m.