Triple
T30750346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marrella |
E782938
|
entity |
| Predicate | hasSoftTissuePreservation |
P183510
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Marrella, hasSoftTissuePreservation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoftTissuePreservation Context triple: [Marrella, hasSoftTissuePreservation, yes]
-
A.
preservationBodyInvolvement
Indicates that an entity participates in or is responsible for activities related to the preservation or conservation of another entity.
-
B.
hasSubjectOfPreservation
Indicates that something is the specific focus or object being preserved or conserved within a preservation relationship.
-
C.
isPreservedBy
Indicates that something remains unchanged, intact, or maintained as it is due to the action or influence of a particular agent or process.
-
D.
hasPreserved
Indicates that one entity has kept another entity intact, unchanged, or maintained in its original or functional state over time.
-
E.
hasTissue
Indicates that one entity possesses, contains, or is associated with a specific tissue of another entity.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: April 29, 2026, 8:38 p.m.