Triple
T5364031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scylla |
E103086
|
entity |
| Predicate | relatedExpressionMeaning |
P8493
|
FINISHED |
| Object | between two dangers |
—
|
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: between two dangers | Statement: [Scylla, relatedExpressionMeaning, between two dangers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedExpressionMeaning Context triple: [Scylla, relatedExpressionMeaning, between two dangers]
-
A.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
B.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
-
C.
meaningOfPhrase
chosen
Indicates that one entity expresses or defines the semantic content or interpretation of a given phrase.
-
D.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
-
E.
semanticRootMeaning
Indicates the fundamental or core meaning that underlies a word, phrase, or expression in a semantic structure.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865d42508190a1a96121674c1020 |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.