Triple
T148610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Age of Sail |
E3382
|
entity |
| Predicate | typicalTechnology |
P1485
|
FINISHED |
| Object | square rigging |
—
|
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: square rigging | Statement: [Age of Sail, typicalTechnology, square rigging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTechnology Context triple: [Age of Sail, typicalTechnology, square rigging]
-
A.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
B.
technologyLevel
Indicates the degree of technological advancement or sophistication associated with an entity relative to others or to a defined scale.
-
C.
technologyParadigm
Indicates a relationship where one entity represents or defines the overarching technological model, framework, or approach within which another entity operates or is categorized.
-
D.
associatedWithTechnology
chosen
Indicates a relationship where an entity is connected to, involved with, or utilizes a particular technology.
-
E.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a257ecb6f48190992c4c8ca908a81c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.