Triple
T28656826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family 1 (Lake Group) |
E725355
|
entity |
| Predicate | hasManuscriptType |
P21654
|
FINISHED |
| Object | continuous-text manuscripts |
—
|
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: continuous-text manuscripts | Statement: [Family 1 (Lake Group), hasManuscriptType, continuous-text manuscripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManuscriptType Context triple: [Family 1 (Lake Group), hasManuscriptType, continuous-text manuscripts]
-
A.
manuscriptType
chosen
Indicates the specific category or kind of manuscript associated with an entity (e.g., draft, final version, annotated copy).
-
B.
hasManuscriptsIn
Indicates that an entity possesses or is associated with manuscripts that are located in a specified place or collection.
-
C.
areManuscriptsOf
Indicates that the subject entities are manuscripts that are versions, copies, or instances of the work represented by the object entity.
-
D.
sendsManuscriptTo
Indicates that one entity transmits or delivers a manuscript to another entity as the intended recipient.
-
E.
manuscriptStatus
Indicates the current state or phase of a manuscript within its creation, review, or publication process.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: April 28, 2026, 4:55 a.m.