Triple
T27083252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Arch Rocks |
E685960
|
entity |
| Predicate | hasNumberOfMajorStacks |
P44200
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Three Arch Rocks, hasNumberOfMajorStacks, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfMajorStacks Context triple: [Three Arch Rocks, hasNumberOfMajorStacks, 3]
-
A.
numberOfStacks
chosen
Indicates the count of distinct stacks associated with or contained within a given entity.
-
B.
hasStacks
Indicates that one entity possesses or contains multiple layered or piled units of another entity.
-
C.
hasAlternativeStack
Indicates that an entity is associated with a different or substitute stack configuration or implementation that can be used in place of the primary one.
-
D.
hasNumberOfMainCascades
Indicates the relationship that specifies how many primary or main cascades (e.g., waterfall drops or major cascade segments) an entity possesses.
-
E.
originalNumberOfStacks
Indicates the initial total count of stacks that existed before any changes or operations were applied.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 8:36 a.m.