Triple
T32291183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Churari Roma |
E824969
|
entity |
| Predicate | partOfBroaderCategory |
P179746
|
FINISHED |
| Object | itinerant craftspeople |
—
|
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: itinerant craftspeople | Statement: [Churari Roma, partOfBroaderCategory, itinerant craftspeople]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfBroaderCategory Context triple: [Churari Roma, partOfBroaderCategory, itinerant craftspeople]
-
A.
partOfBroaderProgram
Indicates that something is a component, segment, or sub-initiative within a larger overarching program.
-
B.
macroCategory
chosen
Indicates that one category functions as a broader, higher-level grouping that encompasses another more specific category.
-
C.
sisterCategory
Indicates a relationship between two categories that share a common parent category, making them parallel or peer categories at the same hierarchical level.
-
D.
broaderProcess
Indicates that one process encompasses, includes, or provides the larger context for another, more specific process.
-
E.
catalogPartOf
Indicates that one catalog item is a component, section, or subset of a larger catalog or cataloged collection.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
Created at: May 1, 2026, 12:44 a.m.