Triple
T37800773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moray |
E942367
|
entity |
| Predicate | hasNumberOfMainDepressions |
P199386
|
FINISHED |
| Object | three |
—
|
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: three | Statement: [Moray, hasNumberOfMainDepressions, three]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfMainDepressions Context triple: [Moray, hasNumberOfMainDepressions, three]
-
A.
hasNumberOfMainSummits
Indicates the relationship that specifies how many primary or main summits are associated with a given entity.
-
B.
hasNumberOfGorges
Indicates the relationship that specifies how many gorges are associated with a given entity.
-
C.
hasNumberOfTroughs
Indicates the relationship that specifies how many troughs (local minima) are present in a given pattern, signal, or function.
-
D.
hasNumberOfMajorIslands
Indicates the quantitative relationship specifying how many major islands are associated with a given entity.
-
E.
hasNumberOfMainCascades
Indicates the relationship that specifies how many primary or main cascades (e.g., waterfall drops or major cascade segments) an entity possesses.
- 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_69f76ee6f1f4819091e2cf9c9e6aee19 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
| PDg | Predicate description generation | batch_69ff32b6dd448190a7a6ebb76b99d4cc |
completed | May 9, 2026, 1:12 p.m. |
Created at: May 3, 2026, 4:19 p.m.