Triple
T25153114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stasinus of Cyprus |
E626232
|
entity |
| Predicate | ancientAttributionBy |
P157970
|
FINISHED |
| Object | later Greek scholars |
—
|
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: later Greek scholars | Statement: [Stasinus of Cyprus, ancientAttributionBy, later Greek scholars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancientAttributionBy Context triple: [Stasinus of Cyprus, ancientAttributionBy, later Greek scholars]
-
A.
cultureAttributedTo
Indicates that a particular cultural style, tradition, or influence is ascribed to or associated with a specific source, group, or origin.
-
B.
reputationInAntiquity
Indicates the reputation or standing an entity had during ancient times.
-
C.
ancientNameOf
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
D.
associatedWithAncientEmpire
Indicates that one entity has a historical, cultural, political, or geographic connection or affiliation with an ancient empire.
-
E.
attestedInInscriptions
Indicates that evidence for the entity is documented or recorded in one or more inscriptions.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f46b84d59881908e038999896aa8f4 |
completed | May 1, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 6:30 a.m.