Triple
T28878962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papius |
E732358
|
entity |
| Predicate | onomasticFunction |
P118939
|
FINISHED |
| Object | indicates membership in the Papii gens |
—
|
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: indicates membership in the Papii gens | Statement: [Papius, onomasticFunction, indicates membership in the Papii gens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onomasticFunction Context triple: [Papius, onomasticFunction, indicates membership in the Papii gens]
-
A.
onomasticType
Indicates the specific kind or category of a name (e.g., personal, place, or other name type) that characterizes the naming relationship.
-
B.
toponymicFunction
Indicates that one entity functions as a place-related name or designation for another entity, typically identifying or characterizing it by a geographic location.
-
C.
namingFunction
Indicates a relationship where one entity serves as the name or naming mechanism assigned to another entity.
-
D.
namedAccordingTo
chosen
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
E.
hasToponymicForm
Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a4d874c819094de2d585e1f5816 |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:41 a.m.