Triple
T16564953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KV15 |
E402436
|
entity |
| Predicate | hasCorridorCount |
P4095
|
FINISHED |
| Object | multiple descending corridors |
—
|
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: multiple descending corridors | Statement: [KV15, hasCorridorCount, multiple descending corridors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorridorCount Context triple: [KV15, hasCorridorCount, multiple descending corridors]
-
A.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
B.
numberOfCorridors
chosen
Indicates the total count of corridors associated with or contained within a given entity or structure.
-
C.
hasCorridorName
Indicates that an entity is associated with or identified by the name of a specific corridor.
-
D.
lengthOfCorridors
Indicates the measured extent or distance of corridors within a given space or structure.
-
E.
hasNumberOfEntrances
Indicates the relationship that specifies how many entrances an entity possesses.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e357711ea481909468147375051bb4 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.