Triple
T17096649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponce de León expedition of 1513 |
E414866
|
entity |
| Predicate | approximateCrewSize |
P883
|
FINISHED |
| Object | about 200 men |
—
|
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: about 200 men | Statement: [Ponce de León expedition of 1513, approximateCrewSize, about 200 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateCrewSize Context triple: [Ponce de León expedition of 1513, approximateCrewSize, about 200 men]
-
A.
crewCountApproximate
chosen
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
B.
crewCount
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
-
C.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
-
D.
hasApproximateNumberOfPeople
Indicates that an entity is associated with an estimated or approximate count of people, rather than an exact number.
-
E.
totalCrewMembers
Indicates the total number of crew members associated with a given entity or context.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfdc9c88190b4e75bbdf4105c1e |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.