Triple
T30927882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venus Pompeiana |
E787906
|
entity |
| Predicate | localFormOf |
P172851
|
FINISHED |
| Object | Venus |
—
|
NE NERFINISHED |
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: Venus | Statement: [Venus Pompeiana, localFormOf, Venus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localFormOf Context triple: [Venus Pompeiana, localFormOf, Venus]
-
A.
realForm
Indicates that one entity is the actual, concrete or physical form or manifestation of another entity (such as an abstract, alternate, or disguised version).
-
B.
standardizedFormOf
Indicates that one entity is the normalized or officially standardized version of another, often consolidating variations or alternative forms into a single canonical form.
-
C.
nativeForm
Indicates that one entity is the original or native linguistic form of another, such as a word’s form in its source language.
-
D.
languageForm
Indicates the specific linguistic form or expression in which something is conveyed or represented.
-
E.
locationFormed
Indicates the place or geographic area where an entity (such as an organization, group, or structure) was originally established or came into existence.
- F. None of above. chosen
Provenance (4 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 29, 2026, 8:51 p.m.