Triple
T35060587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thutmose III’s campaigns in Canaan |
E1011579
|
entity |
| Predicate | hasNumberOfCampaigns |
P90130
|
FINISHED |
| Object | approximately 17 |
—
|
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: approximately 17 | Statement: [Thutmose III’s campaigns in Canaan, hasNumberOfCampaigns, approximately 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfCampaigns Context triple: [Thutmose III’s campaigns in Canaan, hasNumberOfCampaigns, approximately 17]
-
A.
numberOfCampaigns
chosen
Indicates the total count of campaigns associated with or involved in a given entity or context.
-
B.
numberOfCampaignsApprox
Indicates an approximate count of campaigns associated with or relevant to a given entity.
-
C.
hasMarketingCampaign
Indicates that an entity is associated with or utilizes a specific marketing campaign.
-
D.
hasCampaignName
Indicates that an entity is associated with a specific campaign identified by a particular name.
-
E.
hasCampaignStructure
Indicates that one entity possesses, defines, or is associated with a particular organizational or strategic campaign framework of another entity.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:01 p.m.