Triple
T26076563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ship of Theseus |
E657700
|
entity |
| Predicate | firstKnownSource |
P169271
|
FINISHED |
| Object | Plutarch |
—
|
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: Plutarch | Statement: [Ship of Theseus, firstKnownSource, Plutarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstKnownSource Context triple: [Ship of Theseus, firstKnownSource, Plutarch]
-
A.
firstEncounteredBy
Indicates that one entity is the person or agent who initially discovered, met, or came across the other entity for the first time.
-
B.
isBestKnownFrom
Indicates that an entity is primarily or most famously recognized in connection with a particular source, context, or work.
-
C.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
D.
earliestFullSource
chosen
Indicates that one entity is the earliest (in time or order) complete source or origin for another entity.
-
E.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: April 26, 2026, 7:34 p.m.