Triple
T27602730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hierakonpolis Expedition |
E700093
|
entity |
| Predicate | siteTypeStudied |
P162735
|
FINISHED |
| Object | urban center |
—
|
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: urban center | Statement: [Hierakonpolis Expedition, siteTypeStudied, urban center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteTypeStudied Context triple: [Hierakonpolis Expedition, siteTypeStudied, urban center]
-
A.
studyType
Indicates the kind or category of study or research methodology associated with an entity or activity.
-
B.
typeOfResourceStudied
Indicates that a particular resource is the subject or focus of study or analysis in a given context.
-
C.
studType
Indicates a relationship where an entity is classified as a particular type or category of stud (e.g., a specific kind of fastener or structural element).
-
D.
widelyStudiedIn
Indicates that something has been extensively researched, analyzed, or examined within a particular field, domain, or context.
-
E.
studiedWithin
Indicates that one entity pursued studies or academic work within the scope, context, or boundaries defined by another entity (such as an institution, program, or field).
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63097501081909d2b6b969f9a4e2b |
completed | May 2, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 2:08 p.m.