Triple
T12102731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athens Mint |
E288228
|
entity |
| Predicate | startActivityApprox |
P4785
|
FINISHED |
| Object | late 6th century BCE |
—
|
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: late 6th century BCE | Statement: [Athens Mint, startActivityApprox, late 6th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startActivityApprox Context triple: [Athens Mint, startActivityApprox, late 6th century BCE]
-
A.
activityStartContext
Indicates the circumstances, conditions, or situation present at the moment an activity begins.
-
B.
activityStartApprox
chosen
Indicates that the start time of an activity is known only approximately, rather than as an exact timestamp.
-
C.
lastKnownActivity
Indicates the most recent recorded action, event, or state associated with an entity.
-
D.
launchDestination
Indicates the target location or endpoint toward which something is launched or sent.
-
E.
targetedActivity
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.