Triple
T31077731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicus Sandaliarius |
E792011
|
entity |
| Predicate | likelyPrimaryActivity |
P137981
|
FINISHED |
| Object | production of sandals |
—
|
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: production of sandals | Statement: [Vicus Sandaliarius, likelyPrimaryActivity, production of sandals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyPrimaryActivity Context triple: [Vicus Sandaliarius, likelyPrimaryActivity, production of sandals]
-
A.
hasPrimaryActivities
Indicates that an entity is associated with one or more main activities that define its core functions or operations.
-
B.
targetActivity
Indicates that one entity is the intended focus or goal of another entity’s action, operation, or process.
-
C.
primaryActivityPattern
chosen
Indicates the main recurring type of activity or behavior that characterizes how an entity typically operates or functions.
-
D.
targetedActivity
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
E.
primaryIntent
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:02 p.m.