Triple
T17667762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tel Maresha |
E440430
|
entity |
| Predicate | undergroundSystemsExtent |
P128480
|
FINISHED |
| Object | dozens of interconnected cave complexes |
—
|
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: dozens of interconnected cave complexes | Statement: [Tel Maresha, undergroundSystemsExtent, dozens of interconnected cave complexes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergroundSystemsExtent Context triple: [Tel Maresha, undergroundSystemsExtent, dozens of interconnected cave complexes]
-
A.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
B.
railwayTimeUsage
Indicates how much time is spent using or operating a railway within a given context or period.
-
C.
transitDepth
Indicates the measured decrease in observed brightness of an object when another object passes in front of it, blocking part of its light.
-
D.
transitFrequencyApprox
Indicates an approximate rate or regularity with which a transit event or service occurs between entities.
-
E.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46eaaaec8819086977d8a5210c44e |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 9:58 a.m.